Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Security Classification: Dell Proprietary and Confidential. 2010 Dell Inc. All Rights Reserved.
Document Information
Document Information
Document Control
4.2 21st April 2011 Removed references to TP003 and TP015. SEPG
4.3 15th July 2011 QR044 is no longer in use. All references thereto have been removed. SEPG
ii of 29 PM052
Contents
Contents
Tables ................................................................................................................................................. v
Chapter 1 Introduction .................................................................................................................. 6
1 Overview ................................................................................................................................... 6
1.1 Objective ........................................................................................................................ 6
1.2 Scope ............................................................................................................................. 6
1.3 Intended Audience ......................................................................................................... 6
1.4 Acronyms ....................................................................................................................... 6
Chapter 2 Procedure ..................................................................................................................... 7
2 Description ................................................................................................................................ 7
2.1 Process Schematic ........................................................................................................ 7
2.2 Entry Criteria .................................................................................................................. 8
2.3 Inputs.............................................................................................................................. 8
2.4 Tasks .............................................................................................................................. 8
2.5 Outputs ........................................................................................................................... 9
2.6 Exit Criteria ..................................................................................................................... 9
Chapter 3 Test Requirement Analysis Phase ........................................................................... 10
3 Description .............................................................................................................................. 10
3.1 Entry Criteria ................................................................................................................ 10
3.2 Inputs............................................................................................................................ 10
3.3 Tasks ............................................................................................................................ 10
3.4 Outputs ......................................................................................................................... 11
3.5 Exit Criteria ................................................................................................................... 11
Chapter 4 Test Planning Phase .................................................................................................. 12
4 Description .............................................................................................................................. 12
4.1 Entry Criteria ................................................................................................................ 12
4.2 Inputs............................................................................................................................ 12
4.3 Tasks ............................................................................................................................ 12
4.4 Outputs ......................................................................................................................... 14
4.5 Exit Criteria ................................................................................................................... 14
Chapter 5 Test Design Phase ..................................................................................................... 15
5 Description .............................................................................................................................. 15
5.1 Entry Criteria ................................................................................................................ 15
5.2 Inputs............................................................................................................................ 15
5.3 Tasks ............................................................................................................................ 15
5.4 Outputs ......................................................................................................................... 17
5.5 Exit Criteria ................................................................................................................... 17
Chapter 6 Test Execution Phase ................................................................................................ 18
6 Description .............................................................................................................................. 18
6.1 Test Execution- Functional/ System Testing................................................................ 18
6.1.1 Entry Criteria ........................................................................................................ 18
6.1.2 Inputs .................................................................................................................... 18
6.1.3 Tasks .................................................................................................................... 18
6.1.4 Outputs ................................................................................................................. 19
6.1.5 Exit Criteria ........................................................................................................... 20
6.2 Test Execution- Non Functional Testing ...................................................................... 20
6.2.1 Entry Criteria ........................................................................................................ 20
6.2.2 Inputs .................................................................................................................... 20
6.2.3 Tasks .................................................................................................................... 20
PM052 iii of 29
Contents
6.2.4 Outputs................................................................................................................. 21
6.2.5 Exit Criteria .......................................................................................................... 21
Chapter 7 Test Maintenance Phase ........................................................................................... 22
7 Description ............................................................................................................................. 22
7.1 Entry Criteria ................................................................................................................ 22
7.2 Inputs ........................................................................................................................... 22
7.3 Tasks ........................................................................................................................... 22
7.4 Outputs ........................................................................................................................ 23
7.5 Exit Criteria .................................................................................................................. 23
Chapter 8 Metrics ........................................................................................................................ 24
8 Metrics .................................................................................................................................... 24
Chapter 9 Tailoring /Waivers ...................................................................................................... 25
9 Tailoring /Waivers Guidelines ................................................................................................ 25
Appendix A Responsibilities ................................................................................................. 26
Appendix B Related Documents ........................................................................................... 27
Appendix C Severity Classifications..................................................................................... 28
Glossary .......................................................................................................................................... 29
iv of 29 PM052
Tables
Table 1 Acronyms .................................................................................................................................. 6
Table 2 Tasks ........................................................................................................................................ 8
PM052 v of 29
Chapter 1 Introduction
Chapter 1 Introduction
1 Overview
1.1 Objective
This artifact provides a systematic approach to analyze a software item aiming to detect the
differences between existing and required conditions (defect) at each phase of the Testing
Lifecycle of a project.
The six phases of the Testing Lifecycle, described as sub processes to the main Testing
procedure in the document includes:
Test Initiation Phase
Test Requirement Analysis Phase
Test Planning Phase
Test Design Phase Test Execution Phase
Test Maintenance Phase
1.2 Scope
To provide with the detailed approach for conducting manual as well as automated testing at
each phase of the Testing Lifecycle.
1.3 Intended Audience
All Dell Services Applications Services Associates
1.4 Acronyms
Table 1 Acronyms
Acronym Description
CC Configuration Controller
DTS Defect Tracking System
PL Project Leader
PM Project Manager
PPD Project Planning Document
QMS Quality Management System
QOE Quality and Operational Excellence
SME Subject Matter Expert
SRS Software Requirements Specifications
TM Team Member
TRIPS Time and Review Information Processing System
6 of 29 PM052
Chapter 2 Procedure
Chapter 2 Procedure
2 Description
In the document, the procedure for Testing has been structured among six sub processes based on
the six phases of Testing Lifecycle namely:
Test Initiation Phase
Test Requirement Analysis Phase
Test Planning Phase
Test Design Phase
Test Execution Phase
Test Maintenance Phase
The picture below describes various phases of Testing Lifecycle for an application
2.1 Process Schematic
Software Development Lifecycle (SDLC)
Test
Test
Maintenance
Maintenance
7 of 29 PM052
Responsibilities
Step 1 Prepare a high-level resource plan with the list of resources and PM / Test P3MM03-015_PPD_AS.
arrange for allocations Manager - Project Planning
Document_AS/ TP010-
AppTstM Test Plan
Identify channel for communication and plan which may PM / Test P3MM03-015_PPD_AS.
include the following: Manager - Project Planning
Document_AS/ TP010-
Onsite-offshore coordination AppTstM Test Plan
Network connectivity and remote access of test
environment and designated servers
Voice, video, text messaging channel
Step 3 Plan and execute knowledge transfer activities including: PM / Test P3MM03-015_PPD_AS.
Manager - Project Planning
Review of application related artifacts Document_AS/ TP010-
Application walkthrough by Business SME AppTstM Test Plan
Step 4 Plan for transition activities both at onsite and offshore PM / Test P3MM03-015_PPD_AS.
Manager - Project Planning
Document_AS/ TP010-
AppTstM Test Plan
Step 5 Identify and arrange for the training needs required for the PM / Test P3MM03-015_PPD_AS.
project. It may include: Manager - Project Planning
Document_AS/ TP010-
Training on tools AppTstM Test Plan
Any other project specific training
Step 6 Update P3MM03-015_PPD_AS. - Project Planning PM / Test P3MM03-015_PPD_AS.
Document_AS based on the inputs from the above mentioned Manager - Project Planning
steps Document_AS/ TP010-
AppTstM Test Plan
Step 7 Review and analyze requirement, design and functional PM/ Test Lead / P3MM03-220 Review
specification documents received from the Customer and Test Manager Comment Log - AS
identify issues or items that needs clarifications Review Comment Log
Step 8 Resolve and close all the issues identified PM/ Test Lead / P3MM03-220 Review
Test Manager Comment Log - AS
Review Comment Log
8 of 29 PM052
Chapter 2 Procedure Description
TP512- Technical
Problem/ Issue/ Query
Log
2.5 Outputs
P3MM03-015_PPD_AS. - Project Planning Document_AS
Baselined Software Requirement Specification (SRS) document
PM052 9 of 29
Responsibilities
3 Description
The objective of this phase is to review the baselined specification documents to identify the test
coverage, scope and risks involved in testing. It also involves performing testability analysis for
various high-level test scenarios identified.
3.1 Entry Criteria
Baselined Requirement and Functional specifications
Baselined Technical specifications
3.2 Inputs
P3MM03-015_PPD_AS. - Project Planning Document_AS
Baselined Software Requirement Specification (SRS) document
3.3 Tasks
Table 3 Tasks
10 of 29 PM052
Chapter 3 Test Requirement Analysis Phase Description
3.4 Outputs
High-level Test Scenarios
P3MM10-020_RAIDOMatrix_AS - RAIDOMatrix_AS
TP007- Traceability Matrix
PM052 11 of 29
Responsibilities
4 Description
The objective of this phase is to estimate and plan for testing based on the testing objectives,
testability and other analysis conducted at the Requirement Analysis Phase. This also includes
setting up of the test environment.
4.1 Entry Criteria
Identified test objective, scope and coverage
Documented risk analysis and strategy
Identified high- level scenarios for testing
Identified hardware and Software testing requirements
4.2 Inputs
High-level Test Scenarios
P3MM10-020_RAIDOMatrix_AS - RAIDOMatrix_AS
4.3 Tasks
Table 4 Tasks
12 of 29 PM052
Chapter 4 Test Planning Phase Description
PM052 13 of 29
Responsibilities
4.4 Outputs
TP010-AppTstM - Test Plan with defined Test Strategy and Acceptance Criteria
Environment set up
Tools required are set up
14 of 29 PM052
Chapter 5 Test Design Phase Description
5 Description
The objective of this phase is to prepare for Test Execution by designing, developing, validating
and Baselining Test Scenarios, Test Cases, Test Scripts and Test Data
5.1 Entry Criteria
Identified Test objectives, scope and coverage
Baselined Test Plan
Available Test environment
5.2 Inputs
P3MM03-015_PPD_AS. - Project Planning Document_AS
TP010-AppTstM - Test Plan
Test Case Design Techniques (SG090- Guideline for Testing)
5.3 Tasks
Table 5 Tasks
Step 3 Get the sign off from the Customer on the Test Scenarios Test Lead / Test Reviewed Test
Manager / PM Scenarios
Incase the Test Scenarios have been received from Customer
itself, Step 1, 2 and 3 can be avoided.
Step 4 Design and develop Test Cases based on the test scenarios, Test Lead/ TM SRS and other technical
guidelines and technical specifications available documents
It is essential to maintain traceability through SRS, design and
code to test cases using tool. Ensure that all the Customer
requirements have been catered to in the test cases. Also ensure SG090- Guidelines for
the following: Testing
Unit test cases are prepared based on the program
specifications
TP012- Test Case
Integration test cases are prepared against the designated Design
version of the SRS document and the software design
document.
The integration test cases shall indicate the reference
section numbers of the design document.
PM052 15 of 29
Responsibilities
16 of 29 PM052
Chapter 5 Test Design Phase Description
5.4 Outputs
Test Scenarios Functional & Non-Functional
Test Cases - Functional
Test Scripts Functional & Non-Functional
Test Data
Traceability Matrix
PM052 17 of 29
Responsibilities
6 Description
The objective of this phase is to verify and validate the system performance so as to ensure that it
is performing as per the acceptance criteria defined and a defect free delivery is made to the
Customer.
The Test Execution phase has been further sub divided into Functional Testing and Non
Functional Testing
6.1 Test Execution- Functional/ System Testing
6.1.2 Inputs
Test Scenarios
Test Cases
Test Data
Environment set up
Test Tools
6.1.3 Tasks
Table 6 Tasks
18 of 29 PM052
Chapter 6 Test Execution Phase Description
Step 5 Validate the system, once the defect is fixed by conducting TM/ Test Test Scenarios,
Regression and Re- Testing Engineer
TP012- Test Case
Close the defect under the Defect Tracking Tool Design
Test Data
Step 6 Report test progress in the form of Test Status Reports (TP028) PM / Test TP028 Test Status
Manager / Test Report
Lead
TP011-AppTstM-
Project Metrics for
Testing
Step 7 Report, capture and analyze Test Metrics PM / Test TP011-AppTstM-
Manager / Test Project Metrics for
Lead Testing
Step 8 Prepare Final Test Summary Report on completion of the System PM / Test TP029- Final Test
Testing. This report acts as a reference point and provides a Manager / Test Summary Report
summary of testing conducted along with details of test strategies, Lead
test tools, etc. It also provides mapping of test status and test
incidents with function/ requirements tested.
6.1.4 Outputs
PM052 19 of 29
Responsibilities
Metric Reports
6.2.2 Inputs
6.2.3 Tasks
Table 7 Tasks
Test Scripts
Test Data
Step 2 Review Test Logs as part of TP012 and validate test results PM/Test TP012 - Test Case
Manager / Test Design
Lead
Step 3 Detect defect/ issues based on any of the factors: Load / Stress / TL/ Developer/ Test Scenarios,
Volume / Localization / Reliability / Compatibility Architect
TP012- Test Case
Log the defects reported in the Defect Tracking Tool Design Test Case,
20 of 29 PM052
Chapter 6 Test Execution Phase Description
Step 5 Report test progress in the form of Test Status Reports (TP028) PM / Test TP028- Test Status
Manager / Test Reports
Lead
Step 6 Report, capture and analyze Test Metrics PM / Test TP011-AppTstM- Project
Manager / Test Metrics for Testing
Lead
Step 7 Prepare Final Test Summary Report on completion of the System PM / Test TP029- Final Test
Testing. This report acts as a reference point and provides a Manager / Test Summary Report
summary of testing conducted along with details of test strategies, Lead
test tools, etc. It also provides mapping of test status and test
incidents with requirements tested.
6.2.4 Outputs
PM052 21 of 29
Responsibilities
7 Description
The objective of this phase is to ensure defect free delivery of the system once the approved
changes have been incorporated into the system.
7.1 Entry Criteria
Changes incorporated in the system under test on Customers change request
Defect fixes that have triggered change in code
7.2 Inputs
Change Requests
Modified SRS and other technical specifications
7.3 Tasks
Table 8 Tasks
22 of 29 PM052
Chapter 7 Test Maintenance Phase Description
7.4 Outputs
TP012- Test Case Design document with updated execution logs
TP028- Test Status Reports
TP029 Final Test Summary Report
Metrics Report
7.5 Exit Criteria
Test Acceptance Criteria has been met.
Test Summary Reports are available
PM052 23 of 29
Responsibilities
Chapter 8 Metrics
8 Metrics
24 of 29 PM052
Chapter 9 Tailoring /Waivers Tailoring /Waivers Guidelines
This section describes the tailoring process to be carried out for the test execution.
The system testing and acceptance testing phases can be combined together under the
following situations:
As per the Customers requirements
If the Dell Services AS team is working on-site and/or on Customers machine,
with the Customers concurrence
In case a test tool is used, reports generated out of the tool may be used instead of test log and
test incident report
PM052 25 of 29
Responsibilities
Appendix A Responsibilities
Roles Responsibilities
PM / Test Manager Identify the Test Strategy and Acceptance Criteria
Prepare Test Plan
Briefing the team on test documentation
Prepare Test Summary Reports
Liaison with Tool vendors & Infrastructure
PL / Test Lead Conduct Test Readiness Review
Support PM in preparation of Test Strategy, Test Plan and Defect
Root Cause Analysis
Support test team and facilitate testing
Maintain and update for any changes
Create and /or maintain test environment Database setup, Tool
setup etc.
Management of defects using a defect management tool
Regular status reports to Test / Project Manager
PM / Test Manager /PL Plan for knowledge transfer and transition activities
Prepare Test Plan and Test Strategy
Conduct Traceability Analysis
Review Test Log
Conduct Defect Root Cause Analysis
Collate Test Summary Reports for deriving Metrics
Prepare Final Test Summary Report
Test Engineer/ TM Study test documentation including Test strategy, Test Plan, Test
Scenarios etc
Prepare Test Scenarios and Cases and get them reviewed from the
reviewer
Conduct Testing
Document the test results in Test Log.
Log, update and close defects as per retest using a defect tracking
tool
CC Configure all test related documents including Test Data and Test
Results
26 of 29 PM052
Chapter 9 Tailoring /Waivers Tailoring /Waivers Guidelines
PM052 27 of 29
Severity Classifications
28 of 29 PM052
Chapter 9 Tailoring /Waivers Tailoring /Waivers Guidelines
Glossary
Term Definition
Test Case A document specifying inputs, predicted results, and a set of
execution conditions for a test item.
Test Item Software item that is an object of Testing.
Test Plan A document describing the scope, approach, resources, and
schedule of intended Testing Activities.
Test Defects Handling Test defects go through following steps:
Defect Entry - Tester enters a brief description of the defect, the
item tested, item version / build, test phase and the test case id,
which failed. Error log file(s) / Screen (s) that can help to
reproduce and analyze the defect should be attached.
Defect Analysis Analyze the defect for its impact and validity
(is it a real defect?). Valid defects are assigned to a developer.
The defect is classified on a severity level of 1 to 5
Defect Fixing After fixing the defect, the developer enters the
summary of changes made in the code to correct the defect.
Verification Tester verifies the defect fixing by retesting
against the appropriate test cases.
Closure After verification of defect fixing, the defect is
closed.
PM052 29 of 29