Scribd
Upload
53 views2 pages

What Is Test Strategy

The document discusses test strategy, which is the test levels and activities that will be performed to test a product. It provides examples of different types of test strategies like requirements based, risk based, and model based testing. It also discusses how a test summary report communicates test results and findings to stakeholders after testing is completed.

Uploaded by

alakh400
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
53 views2 pages

What Is Test Strategy

The document discusses test strategy, which is the test levels and activities that will be performed to test a product. It provides examples of different types of test strategies like requirements based, risk based, and model based testing. It also discusses how a test summary report communicates test results and findings to stakeholders after testing is completed.

Uploaded by

alakh400
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

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. . ". $. &. '. ). +. -. Analytical !isk based test strategy !e#uirements based test strategy %odel based %ethodical (rocess compliant *ynamic ,onsultative or *irected !egression 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. .f further testing is re#uired and we need to delay the release. Test summary report will be different for different kind of testing. /uppose 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 re#uirements based testing then your test summary report should measure coverage against the re#uirements. .n 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 identifier /ummary 0ariances ,omprehensive assessment /ummary of results 1valuation /ummary of activities Approvals

You might also like