...
The provided narrative should be more elaborate than in the test status reports.
Summary
It recapitulates the evaluation of the test items. Although the test completion report can reflect the structure of the test status report, the details that were only temporarily significant can be omitted from it. The table rows or subsections should correspond to the test items or scenarios listed in the project plantest design specification. The summary should indicate the versions of the items that were tested, as well as the used testing environment. For each item it should be briefly explained what was tested and what was the outcome.
...
All variations and discrepancies from the original test plan should be noted here. This section can also provide an assessment of differences between the test environment and the operational environment and their effect on the test results.
Test Results
This is a comprehensive interpretation of the test results. Include description of issues or defects discovered during the testing. Also describe the unexpected results and problems that occurred during the testing. For resolved incidents, their resolutions should be summarised. For unresolved test incidents, an approach their resolution should be proposed.
...
Test Design Specification
The Use Case is a high level description of a specific system usage, or set of system behaviours or functionalities. It should not be mistaken for UML use case. It implies, from the end-user perspective, a set of tests that need to be conducted in order to consider the system as operational for particular type of use. It therefore usually describes the system usage, features and related requirements and that are necessary for utilization of the system by end users on regular basis.
Requirement is a high level description of necessary capability, feature, functionality, characteristic or constraint that the system must meet or be able to perform. It is a statement that identifies a necessary quality of a system for it to have value and utility to a user, customer, organization, or other stakeholder. It is necessary for the fulfillment of one or several Use Cases or usage scenarios (in Scenario Testing).
The requirements specification is an explicit set of requirements to be satisfied by the system which is to be developed, and is therefore produced quite early in its development. Such a specification may be a direct input for testing process, as it lays out all requirements that were, hopefully, addressed during the system development.
Functional
Non-functional
Test design specification addresses the test objectives by refininig the features to be tested, test cases, expected results and test pass criteria. This document groups related test items together.
Features to be Tested
This section identifies the test items and describes the features and combinations of features that the subject of testing.
Level of testing appropriate to test item if the test design specification covers more than one level of testing.
Reference to the original documentation where this test objective (feature) was obtained.
Attributes and Characteristics
Groupings of Features
The features may be grouped around the few key applications or use cases.
The Use Case is a high level description of a specific system usage, or set of system behaviours or functionalities. It should not be mistaken for UML use case. It implies, from the end-user perspective, a set of tests that need to be conducted in order to consider the system as operational for particular type of use. It therefore usually describes the system usage, features and related requirements and that are necessary for utilization of the system by end users on regular basis.For each feature or feature combination, a reference to its associated requirements in the item requirement specification or design description should be included.
On the base of identified features, the requirements are defined.
Requirement is a high level description of necessary capability, feature, functionality, characteristic or constraint that the system must meet or be able to perform. It is a statement that identifies a necessary quality of a system for it to have value and utility to a user, customer, organization, or other stakeholder. It is necessary for the fulfillment of one or several use cases or usage scenarios (in scenario testing).
The requirements specification is an explicit set of requirements to be satisfied by the system, and is therefore usually produced quite early in its development. Such a specification may be a direct input for testing process, as it lays out all requirements that were, hopefully, addressed during the system development. Alternatively, the requirements that are directly associated with testing can be formulated, without the prior input of requirements produced during development.
Functional
Non-functional
Scenario Testing is a higher level approach to testing of complex systems that is not based on Test Cases, but on working through realistic and complex stories reflecting user activities. These stories may consist of one or several user stories,which capture what a user does or needs to do as part of his or her job function, expressed through one or more sentences in the everyday or domain language. The tester who follows the scenario must interpret the results and evaluate whether they can be considered as a pass or failure. This interpretation may require backing by domain experts. This term should be distinguished from Test Procedure and Test Case scenario.
The requirements are the base for elaboration of the test cases.
Approach Refinements
Specify refinements to the approach described in the test plan. Include specific test techniques to be used.The method of analyzing test results should be identified (e.g., comparator programs or visual inspection).
Also deviations from the plan
Test Cases
Identify test cases.
Some test cases may be related to several use cases.
List the identifier and a brief description of each test case associated with this design. A particular test case may be identified in more than one test design specification. List the identifier and a brief description of each procedure associated with this test design specification.
Specify the results of any analysis that provides a rationale for test case selection. For example, one might specify conditions that permit a determination of error tolerance (e.g., those conditions that distinguish valid inputs from invalid inputs).
Summarize the common attributes of any test cases. This may include input constraints that must be true for every input in the set of associated test cases, any shared environmental needs, any shared special procedural requirements, and any shared case dependencies.
Representation of test case traceability is modeled through the Test Matrix.
Feature Pass/Fail Criteria
Specify the criteria to be used to determine whether the feature or feature combination has passed or failedScenario Testing is a higher level approach to testing of complex systems that is not based on Test Cases, but on working through realistic and complex stories reflecting user activities. These stories may consist of one or several user stories,which capture what a user does or needs to do as part of his or her job function, expressed through one or more sentences in the everyday or domain language. The tester who follows the scenario must interpret the results and evaluate whether they can be considered as a pass or failure. This interpretation may require backing by domain experts. This term should be distinguished from Test Procedure and Test Case scenario.
Test Case Specification
The Test Case is a specification of criteria that need to be met in order to consider some system feature, set of features or Use Case as working. It is the smallest unit of testing and is sometimes colloquially referred as Test. It should include a description of the functionality to be tested, and the preparation required to ensure that the test can be conducted. A single test case is sometimes associated with several requirements. It may be partially or fully automated.
...