You are on page 1of 4

Deliverable: TE580 Test Plan

Domains: Testing

Expand All Sections Collapse All Sections


Main Description
The Test Plan is a composite deliverable that includes the following children deliverables:
The Test Approach builds on the testing strategy created in the planning stage and
explains the objectives and scope of the test, entry and exit criteria, resources, key dates,
etc.
The Test Scenarios and Test Conditions and Expected Results (TCER) explain
what to test and how to carry out the test at a high level.
The Test Cycle Control Sheet (TCCS) defines when and by whom test cycles are
executed.
Test Script details the exact steps that a tester must follow to complete testing (i.e., to
test all the test scenarios and conditions). Test Script also includes the data that is used
for testing.
Together, the TCCS and the associated Test Scripts form the part of the Test Plan to be used by
the test execution team. The TCCS is used to manage the execution schedule, since it lists every
cycle that is executed, along with the associated start and stop dates and resources. The test
scripts are followed by the testers and are used to document actual results.
When appropriate, use the Test Plan Template to document test conditions, scripts, test cycle
control sheets, etc., in one document, rather than creating these as separate deliverables. Note
that the Test Approach document must be created separately.
Volume: One for each test stage: component test, assembly test, product test, performance test,
etc.
Back to top
Illustrations
For templates and examples in addition to those listed below, see the Accenture Delivery
Methods Repository.
Templates Test Plan Template
Reusable Assets Defect Tracking and Processing Procedures
Test Execution Procedures
Test Planning Procedures
Back to top
Deliverable Properties
Deliverable Parts TE582 Test Approach
TE583 Test Scenarios
TE584 Test Conditions and Expected Results
TE585 Test Cycle Control Sheet
TE586 Test Script

Back to top
Key Considerations
The following people use this information:
The test lead uses this deliverable to plan the work for the test.
The tester uses this deliverable to execute the test.
The project manager uses this deliverable as an input to create and maintain the project work
plan and technology implementation plan.
Back to top
Relationships
Categories Work Products - Alphabetical
Roles Responsible:
Tester
Test Lead
Modified By:
Application Designer
Developer
Human Performance Developer
Project Manager
Technical Architect
Technical Designer
Tester
Test Lead
Tasks Input To:
2191 Confirm Application Analysis Deliverables
2391 Confirm Technical Architecture Analysis Deliverables
3182 Plan Assembly Test
3191 Confirm Application Design Deliverables
3391 Confirm Technical Architecture Design Deliverables
4188 Build and Test Application Components
4191 Confirm Application Build
4345 Install and Build Development Environment
4355 Install and Build Execution Environment
4365 Install and Build Operations Environment
4545 Develop Performance Support Materials
4591 Confirm Change Enablement Materials
5128 Prepare and Execute Assembly Test
5131 Confirm Assembly-tested Application
5148 Prepare and Execute Product Test
5158 Prepare and Execute Performance Test
5168 Perform Mock Conversion
5171 Confirm Product-tested Application
5188 Prepare and Execute User Acceptance Test
5191 Confirm User-accepted Application
5328 Prepare and Execute Technical Architecture Assembly Test
5538 Test Training and Performance Support Materials
6118 Prepare for Migration
6148 Perform Operational Readiness Test

T2199 Transition Application Analysis Deliverables


T2399 Transition Technical Architecture Analysis Deliverables
T3199 Transition Application Design Deliverables
T3399 Transition Technical Architecture Design Deliverables
T4199 Transition Application Build
T4399 Transition Technical Architecture Build
T4599 Transition Change Enablement Materials
T5139 Transition Assembly-tested Application
T5179 Transition Product-tested Application
T5199 Transition User-accepted Application
T5399 Transition Tested Technical Architecture
4391 Confirm Technical Architecture Build
4535 Develop Training Materials
5391 Confirm Tested Technical Architecture
Output From:
1035 Manage Suppliers
2191 Confirm Application Analysis Deliverables
2391 Confirm Technical Architecture Analysis Deliverables
3191 Confirm Application Design Deliverables
3382 Plan Technical Architecture Component and Assembly Test
3391 Confirm Technical Architecture Design Deliverables
4183 Plan Component Test
4188 Build and Test Application Components
4191 Confirm Application Build
4345 Install and Build Development Environment
4355 Install and Build Execution Environment
4365 Install and Build Operations Environment
4391 Confirm Technical Architecture Build
4535 Develop Training Materials
4545 Develop Performance Support Materials
4591 Confirm Change Enablement Materials
5128 Prepare and Execute Assembly Test
5131 Confirm Assembly-tested Application
5148 Prepare and Execute Product Test
5158 Prepare and Execute Performance Test
5168 Perform Mock Conversion
5171 Confirm Product-tested Application
5188 Prepare and Execute User Acceptance Test
5191 Confirm User-accepted Application
5328 Prepare and Execute Technical Architecture Assembly Test
5391 Confirm Tested Technical Architecture
6118 Prepare for Migration
6148 Perform Operational Readiness Test
Back to top
More Information
Concepts Testing Concepts Overview
Testing Framework Overview
Guidelines Testing Guidelines for Distributed Work
Testing Management Guidelines
Testing Metrics

Supporting Materials Accenture Delivery Tools Home Page


Accenture Delivery Tools
Back to top
2008 Accenture. All Rights Reserved. The trademarks used in these materials are the properties
of their respective owners. This work is protected by copyright law as an unpublished work and
contains valuable trade secrets and confidential information. For use by Accenture personnel or
on Accenture projects.
Privacy Statement

You might also like