Test plans. Test Plans A test plan states: What the items to be tested are At what level they will be tested What sequence they are to be tested in How.

Similar presentations

Presentation on theme: "Test plans. Test Plans A test plan states: What the items to be tested are At what level they will be tested What sequence they are to be tested in How."— Presentation transcript:

1
Test plans

2
Test Plans A test plan states: What the items to be tested are At what level they will be tested What sequence they are to be tested in How the test strategy will be applied to the testing of each item A description of the test environment.

4
What to consider for the Test Plan 5. Software Risk Issues 6. Features to be Tested 7. Features not to be Tested 8. Approach 9. Item Pass/Fail Criteria 10. Suspension Criteria and Resumption Requirements

6
What I want included in the test plan List of responsibilities (and who does them) Who runs the test Who approves the results Unit tests to be run with expected results Objectives Approach Include a description of the type of data used for unit testing and why that data is being used Pass/fail criteria When the tests are to be run (timeline)

7
What I want included in the test plan Integration tests to be run with expected results Objectives Approach Include a description of the type of data used for integration testing and why that data is being used Pass/fail criteria When the tests are to be run (timeline)

8
What I want included in the test plan Systems/Acceptance tests to be run with expected results Objectives Approach Include a description of the type of data used for systems/acceptance testing and why that data is being used Pass/fail criteria When the tests are to be run (timeline)

9
What I want included in the test plan Alpha testing to be done Objectives Approach Features to be tested Pass/fail criteria When the tests are to be run (timeline)

10
What I want included in the test plan Beta testing Objectives Approach Who is participating in the beta testing Pass/fail criteria What I want included in the test plan

11
Deliverables Test Design Specification: detailing test conditions and the expected results as well as test pass criteria. Test Case Specification: specifying the test data for use in running the test conditions identified in the Test Design Specification

12
Deliverables Test Procedure Specification: detailing how to run each test, including any set-up preconditions and the steps that need to be followed Test Item Transmittal Report: reporting on when tested software components have progressed from one stage of testing to the next

13
Deliverables Test Log: recording which tests cases were run, who ran them, in what order, and whether each test passed or failed

14
Deliverables Test Incident Report: detailing, for any test that failed, the actual versus expected result, and other information intended to throw light on why a test has failed. These include the expected results being wrong, the test being run wrongly, or inconsistency in the requirements meaning that more than one interpretation could be made.

15
Deliverables- Test Incident Report The report consists of all details of the incident such as actual and expected results, when it failed, and any supporting evidence that will help in its resolution. The report will also include, if possible, an assessment of the impact of an incident upon testing.

16
Deliverables- Test Summary Report Test Summary Report: A management report providing any important information uncovered by the tests accomplished, and including: Assessments of the quality of the testing effort The quality of the software system under test, and statistics derived from Incident Reports.

17
Deliverables- Test Summary Report The report also records: What testing was done How long it took in order to improve any future test planning. This final document is used to indicate whether the software system under test is fit for purpose according to whether or not it has met acceptance criteria defined by project stakeholders