Software test documentation: Difference between revisions

Revision as of 12:14, 7 August 2019

Revision as of 16:06, 30 January 2020

Line 19:

*'''Level Test Log''' (LTL): To provide a chronological record of relevant details about the execution of tests, e.g. recording which tests cases were run, who ran them, in what order, and whether each test passed or failed.

*'''Anomaly Report''' (AR): To document any event that occurs during the testing process that requires investigation. This may be called a problem, test incident, defect, trouble, issue, anomaly, or error report. This document is deliberately named as an anomaly report, and not a fault report. The reason is that a discrepancy between expected and actual results can occur for a number of reasons other than a fault in the system. These include the expected results being wrong, the test being run incorrectly, or inconsistency in the requirements meaning that more than one interpretation could be made. 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.

*'''Level Interim Test Status Report''' (LITSR): To summarizesummarise the interim results of the designated testing activities and optionally to provide evaluations and recommendations based on the results for the specific test level.

*'''Level Test Report''' (LTR): To summarizesummarise the results of the designated testing activities and to provide evaluations and recommendations based on the results after test execution has finished for the specific test level.

*'''Master Test Report''' (MTR): To summarizesummarise the results of the levels of the designated testing activities and to provide evaluations based on these results. This report may be used by any organizationorganisation using the MTP. 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 Anomaly Reports. The report also records what testing was done and 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.

==Use of IEEE 829==