What is Test Strategy

The test levels to be performed in testing and the description of testing activities within those test levels is known as test strategy.

There are many types of test strategy and selection of appropriate test strategy is the major factor behind testing success.

Test strategy also comes in test deliverables, the test strategy which is followed for testing should be informed to the project stakeholders.

Following are the major types of test strategies that are followed in software testing:

1. Analytical2. Risk based test strategy3. Requirements based test strategy4. Model based5. Methodical6. Process compliant7. Dynamic8. Consultative or Directed9. Regression averse

Test Execution Report or Test Summary Report

Test summary report is a document which contains summary of test activities and final test results.

After the testing cycle it is very important that you communicate the test results and findings to the project stakeholders so that decisions can be made for the software release. i.e. If further testing is required and we need to delay the release.

Test summary report will be different for different kind of testing. Suppose you are doing risk based testing your report should contain the test coverage and unresolved defects against the product risks, and if you are doing requirements based testing then your test summary report should measure coverage against the requirements.

In addition to test coverage and unresolved defects test summary reports should also contain test strategy, test objectives and overall result of test effort.

IEEE 829 standard Test Summary Report Template

Test summary report identifierSummaryVariancesComprehensive assessmentSummary of resultsEvaluationSummary of activitiesApprovals