iTM <Project Name> Test Completion Report (Template) General Instructions This template includes guidelines or sample text which look like this – boxed (or unboxed), red text. Remove them once you understand how to use the template. It also includes text marked in blue, which should be replaced with the appropriate information for the relevant project. Text in grey is suggested standard text, which may be replaced with content more appropriate to your project, if preferred. Black or plum text relates to the structure of the document and should not normally be replaced. This template can be used for to report test completion for the project prior to product implementation. All sections of this template should be included. If a section is not relevant, enter a rationale to that effect. Document Owner Date State / Version Configuration Item # Assess | Visualise | Transform | Manage | Train
12
Embed
Test Completion Report (Template) · iTM Test Completion Report (Template) General Instructions This template includes guidelines or sample
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
iTM
<Project Name> Test Completion Report (Template)
General Instructions
This template includes guidelines or sample text which look like this – boxed (or unboxed), red text. Remove them once you understand how to use the template.
It also includes text marked in blue, which should be replaced with the appropriate information for the relevant project.
Text in grey is suggested standard text, which may be replaced with content more appropriate to your project, if preferred.
Black or plum text relates to the structure of the document and should not normally be replaced.
This template can be used for to report test completion for the project prior to product implementation.
All sections of this template should be included. If a section is not relevant, enter a rationale to that
CONFIDENTIALITY & COPYRIGHT INFORMATION ......................................................................................................... 2
1. DOCUMENT CONTROL ........................................................................................................................................ 3
1.1. APPROVAL RECORD ................................................................................................................................................... 3 1.2. DOCUMENT HISTORY ................................................................................................................................................. 3 1.3. REFERENCES ............................................................................................................................................................ 3 1.4. TEMPLATE HISTORY ................................................................................................................................................... 3
2.2. ASSUMPTIONS ......................................................................................................................................................... 4 2.3. THE TEST PROCESS .................................................................................................................................................... 4 2.4. QUALITY AND PRODUCT RISK ....................................................................................................................................... 5 2.5. RECOMMENDATIONS ................................................................................................................................................. 5
3. TEST SUMMARY ................................................................................................................................................. 6
This document should be used to provide a summary of the completion of test activities covering all test levels and should be supported by the completed Test Measurement Report.
2.1. Purpose
This document is the test completion report for the <project name> project. The purpose of this document is to:
Serve as the final release document, confirming the end of all test levels for the <Project name> project in scope of the test plan
Describe the tests performed during the <project name> project Describe any variance from the planned scope of testing Summarise incidents raised and addressed during testing Summarise incidents outstanding at the end of testing, providing details of responsibility and
planned timescales for resolution Describe conclusions drawn from test execution Provide an indication of the quality of the object under test Provide an account of how objectives in test plans have been met Provide a summary of the product risks mitigated by testing.
Management summary
2.2. Assumptions
Detail the assumptions made using text from relevant test plans. Include additional assumptions made during test activities.
2.3. The test process
Provide a summary of the quality of the test process as implemented. Provide a summary of the activities performed during the project test life cycle.
Provide a summary of what went well and what did not go so well (in terms of main processes). Give an account of planned and actual start and end dates, effort and resources. List planned activities that were not undertaken and explain their omission. If deadlines were not met, explain why. Appropriate reference should be made to KPIs T2, T2a and all of T3.
Provide a summary of the overall status of quality criteria (entry / exit) achievement (referencing KPI T1a).
Provide a brief explanation of what was being tested (system, application and hardware).
Provide a brief summary of overall KPI achievement / non-achievement. These can be extracted from the Test Measurement Report. Specifically indicate KPI T4c – successfully tested requirements coverage.
Briefly describe any KPIs not achieved and the resulting residual risks.
Summarise the numbers of product risks that were to be addressed (insert the graph from the test product risk catalogue) and provide a brief explanation of how the approach to testing mitigated those risks (for example, using text from the relevant test plan).
An example is:
2.5. Recommendations
Briefly describe whether product risks have been sufficiently mitigated and if testing has achieved its objective to demonstrate adequate levels of product quality. These details will be used to inform the decision to promote
to the live environment. If the recommendation is not to proceed to live, provide a full explanation.
Based on the results of product risk mitigation activities outlined above and the final summary of KPI results, our recommendation is to <proceed/not proceed>.
0 5 10 15 20
Baseline
Last Period
Current
4
4
7
20
11
19
6
6
6
6
4
4
Current Product Risk Status(based on Risk Severity Rating)