Artifact: Test
Results
|
A collection of summary information determined from the analysis of one or more Test Logs and Change Requests, providing a relatively detailed assessment of the quality of the Target Test Items and the status of the test effort. Sometimes referred to as a larger repository of many Test Results. |
|---|---|
| Role: | Test Analyst |
| Optionality/Occurrence: | We recommend you determine and record Test Results, and retain these results as an essential testing artifact. |
| Templates and Reports: |
|
| Examples: | |
| UML Representation: | Not applicable. |
| More Information: |
| Input to Activities: | Output from Activities: |
Purpose 
Test Results are used to record the detailed findings of the test effort and to subsequently calculate the different key measures of testing.
Brief Outline
The information (as opposed to raw data) contained by the Test Results may vary depending on the technology and tools used both during test execution to capture the test log, and after the fact to conduct analysis of the raw Test Log data. Here are some ideas for data that can be determined, and made available for review and evaluation:
- Test Results identifier (ID for identifying these Test Results from others)
- time, date, name of tester, and environment information (such as O/S, machine characteristics, and so forth)
- specific identification of the Target Test Items (such as version, objects, and files)
- Test Cases intended to be executed (and traced to the requirements for test)
- Test Cases executed (and traced to the requirements for test)
- size measurement of Target Test Items to be executed
- size measurement of Target Test Items executed
- response time for specified sequences of events
- trace data containing the details of the conversations between actors and the Target Test Items, and/or between objects in the Target Test Items.
- actual result of each Test Case executed
- differences between expected result and actual result
- an indication of pass or fail for each Test Case executed
- actual level of completeness and positive results from each Test Suite executed
- any unexpected or abnormal results or behaviors
Properties
There are no UML representations for these properties.
Property Name |
Brief Description |
|---|---|
| Name | An unique name used to identify these Test Results. |
| Description | A short description of the contents of the Test Results, typically giving some high-level indication of complexity and scope. |
| Purpose | An explanation of what these Test Results represents and why they are important. |
| Dependent Test and Evaluation Items | Some form of traceability or dependency mapping to specific elements such as individual requirements that need to be referenced. |
Timing
The Test Results need to be determined whenever test and evaluation execution occurs. Since test execution may occur many times during the development lifecycle, test results should be determined and stored in such a way that they can be reviewed and evaluated individually for each instance of test execution.
Responsibility
The Test Analyst role is primarily responsible for this artifact. Those responsibilities include:
- reviewing Test Logs and Change Requests
- actively monitoring for anomalous and erroneous occurrences in the Test Log, investigating and reporting a conclusion
- ensuring the accurate analysis of the observed outcome of each test conducted in the test execution cycle
- ensuring the Test Results are uniquely and accurately identified and recorded against the correct test execution cycle
Tailoring
If you are using automated test tools, such as those found in Rational Suite or Test Studio, a lot of the determination of the above information can be simplified by the analysis capabilities of the tools. The tools also offer saved and customizable views of the information for reporting purposes.
Sometimes the test results are referenced from or enclosed directly within a Test Evaluation Summary.
