A three step approach for testing products from the best practices observed in a wide variety of successful testing projects.
1. Test Strategy
2. Test Planning
3. Test Execution
A product's test strategy ties its release and sign-off criteria to its business objectives.
The overall testing strategy is defined in collaboration with the customer. This involves figuring out the order for scheduling so that test planning, test case design, test automation and test execution take into account key dependencies.
*
completion of low- and high-level specifications;
*
code-complete;
*
completion of component unit-testing (when QA can begin integration testing);
*
UI-freeze (after which QA can be confident that (a) UI level automation will not break repeatedly due to fluctuating UI and screen layouts, and (b) that API-level automation will not be undermined by changes in interfaces/API's).
The key activities we carry out are as follows:
*
Define project scope & commitments
*
Define terms of reference
*
Set customer expectations
*
Tie together the business objectives of the STQE project with the release/sign off criterion and associated testing activity
*
Integrate the STQE processes with development lifecycle
*
Partition the problem into manageable test plans
*
Identify key dependencies & tradeoffs
*
Scope resource requirements
Test Planning
The key steps during Test Planning are as follows :
*
Define release criteria (with the release manager)
*
Outline and prioritize the testing effort.
*
Chart test automation requirements
*
Identify resource requirements at various stages of testing
*
Set up calendar-based activity plan
*
State reporting mechanism & establish communication model
*
Configure team including number, type, and seniority of resources and length of time required, mapped each resource onto the activity plan.
Test Execution
*
Prepare comprehensive test plan specifications and test cases for each level of testing.
*
Review all test plans and test cases
*
Prepare test data and test logs.
*
Set up the test environment so that all operations can be completed promptly, accurately, and efficiently.
*
Execute Error/Trap tests to ensure testers accuracy.
*
Execute tests as described, noting where testcases require revision and updating.
*
Report all bugs in the manner agreed upon with the customer, following all defect management protocols, informing customer of current status, monitoring and driving to resolution all red-flag conditions, and ensuring that communication between all parties is complete and accurate.
*
Run spot checks to ensure quality.
*
Update weekly the Project Health Status document for Internal Audit & Tracking.
*
When the project has been completed, review all aspects of the project and submit a Project Retrospective report to the customer that objectively evaluates the project's execution.
Software Testing Areas 
Functionality Testing is performed to verify that a software application performs and functions correctly according to the design specifications. .
