Testing strategy

Unit, integration, and system levels of testing

Functional, regression, and acceptance testing approaches

Cross Browser Compatibility testing

Automated API regression

The testing of all functional requirements using existing test cases for the

a defined list of the user stories

Identifying the successive types of testing to be undertaken throughout the

lifecycle of development to live operations

The following are considered out of scope for the Test

Strategy and testing scope:

• Performance testing
• Security testing
• Automated UI regression
• User Documentation Review

1.1. General

Exploratory Testing is be carried out once the build is ready for testing

The QA team is provided with access to all Test environments

The QA team assumes all necessary inputs required during test design and

execution will be supported by Development/Product teams appropriately

Test case design activities will be performed by QA team 

Test environment and preparation activities will be owned by DEV Teams

The project will provide test planning, test design, and test execution support

QA team will manage the testing effort in close collaboration with the product team

Project team has the knowledge and relevant experience or received

adequate training in the system, the project, and the testing processes

The system will be treated as a black box: if the information shows correctly

online and in the reports/logs, it will be assumed that the database is

working properly

During functional testing, the QA team will use preloaded data which is

available in the system at the time of execution