Artifact: Test Findings |
This artifact summarizes 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.
Domains: Test
Purpose
To record the detailed findings of the test effort To subsequently calculate the different key measures of testing
Relationships
Fulfilled Slots | [Technical Test Results]
Roles | Responsible: Security Auditor Security Developer Security Tester Test Analyst | Modified By: Security Auditor Security Developer Security Tester Test Analyst Tester
Tasks | Input To: Build Reports Evaluate Performance Test Evaluate Security Risks Fix Vulnerabilities Determine Test Results Monitor Test Effort | Output From: Analyze Test Failure Conduct Security Assessment Determine Test Results Fix Vulnerabilities Run Performance Test
Description
Main Description | Test Findings are sometimes a large set of many Test Findings.
Brief Outline | The information (as opposed to raw data) contained by the Test Findings 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 then made available for review and evaluation: Test Findings identifier (ID for identifying these Test Findings from others) Time, date, name of tester, and environment information (such as O/S, machine characteristics, and so on) 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, 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
Tailoring
Impact of not having | Without this or similar documentation, there is no record of which tests were executed successfully, what variances were discovered, and what action was taken. If this information is not available: There will be no way to know which tests passed and which failed. There will be no way to assess the status of testing and the quality of the product at that level of testing. It will be difficult to know how many tests remain outstanding.
Reasons for not needing | If the testing being done is relatively simple then a separate formal set of findings may not be necessary as the information captured as part of the overall testing summary may be sufficient.
Representation Options | If you are using automated test tools, 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.
More Information
Concepts | Testing Qualitative Requirements
© Copyright IBM Corp. 1987, 2009. All Rights Reserved. © Copyright ABC Corp. 2009. All Rights Reserved. Includes materials licensed from IBM and Eclipse. See IBM copyright and Eclipse copyright .