Artifact: Test Evaluation Summary |
The Test Evaluation Summary organizes and presents a summary analysis of the Test Results and key measures of test for review and assessment, typically by key quality stakeholders. In addition, the Test Evaluation Summary may contain a general statement of relative quality, and provide recommendations for future test effort.
Domains: Test
Purpose
To support objective quality evaluation. To enable the communication between the main stakeholders. To support interim evaluations of quality. To present recommendations about the next test efforts required.
Relationships
Fulfilled Slots | [Project Status]
Roles | Responsible: Security Auditor Security Tester Test Manager | Modified By: Security Auditor Security Tester Test Analyst Test Manager
Tasks | Input To: Monitor Test Effort Design Performance Test Establish Performance Test Goals Evaluate Security Risks Fix Vulnerabilities Refine Test Process Comunicate Test Project Status Monitor Test Effort Refine Test Process | Output From: Build Reports Comunicate Test Project Status Determine Test Results Evaluate Performance Test Evaluate Security Risks Monitor Test Effort
Illustrations
Templates | Test Evaluation Summary Report (Formal) Test Evaluation Summary Report (Informal)
Reports | AppScan Compliance AppScan Executive Summary AppScan Industry Standard AppScan Remediations Tasks Appscan Security Issues
Tailoring
Impact of not having | This is a key artifact which enables the communication between the main stakeholders. Without its summary of findings and risks, showing the progress against quality measures as defined in the detailed test plans, there are significantly greater opportunities for misunderstandings. These misunderstandings may lead to reduced product quality. If no formal test reporting is to be done, frequent and consistent informal communication is necessary, particularly of defect management activity and its implications for the project. It would be wise to keep an informal record of these communications as well.
Reasons for not needing | In small or very automated testing projects, there may be less need for formalized reporting at any point in time or at milestones, although a conclusive set of findings should not be omitted. In these circumstances, it is assumed that informal communication or automated reporting will provide the project team with a clear picture of test status.
Representation Options | The level of formality and presentation format for this work product vary widely. Some produce simple text document reports, whereas others produce full-fledged presentations. Both formats may be useful to emphasize certain critical test cycles and de-emphasize others. The Test Evaluation Summary may be enclosed as part of another evaluation document (such as an iteration assessment or review record).
More Information
Checklists | Performance Analysis
Concepts | Key Measures of Test
Guidelines | Performance Test Report
© 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 .