SlideShare a Scribd company logo
1 of 13
Download to read offline
Software Test Plan (STP) Template
Items that are intended to stay in as part of your document are in
bold; explanatory comments are in italic text. Plain text is used
where you might insert wording about your project.
This document is an annotated outline for a Software Test Plan,
adapted from the IEEE Standard for Software Test Documentation
(Std 829-1998).
Tailor as appropriate. Where you decide to omit a section, you might
keep the header, but insert a comment saying why you omit the
element.
Testplan
Agency Name
Project Name
Software Quality Assurance Plan
Version: (n) Date: (mm/dd/yyyy)
Document History and Distribution
1. Revision History
Revision # Revision Date Description of Change Author
2. Distribution
Recipient Name Recipient Organization Distribution Method
Software Test Plan
7/21/2013 1:40:54 PM i
TABLE OF CONTENTS
1. INTRODUCTION....................................................................................................................................................1
2. TEST ITEMS...........................................................................................................................................................3
3. FEATURES TO BE TESTED ...............................................................................................................................4
4. FEATURES NOT TO BE TESTED......................................................................................................................4
5. APPROACH ............................................................................................................................................................4
6. PASS / FAIL CRITERIA ........................................................................................................................................6
7. TESTING PROCESS.............................................................................................................................................6
8. ENVIRONMENTAL REQUIREMENTS...............................................................................................................7
9. CHANGE MANAGEMENT PROCEDURES.......................................................................................................8
10. PLAN APPROVALS ............................................................................................................................................8
Software Test Plan
7/21/2013 1:40:54 PM 1
1. INTRODUCTION
(NOTE 1: THE SOFTWARE TEST PLAN GUIDELINES WERE DERIVED AND
DEVELOPED FROM IEEE STANDARD FOR SOFTWARE TEST
DOCUMENTATION (829-1998)).
(Note 2: The ordering of Software Test Plan (STP) elements is not meant to imply
that the sections or subsections must be developed or presented in that order. The
order of presentation is intended for ease of use, not as a guide to preparing the
various elements of the Software Test Plan. If some or all of the content of a section
is in another document, then a reference to that material may be listed in place of
the corresponding content.)
The Introduction section of the Software Test Plan (STP) provides an overview of the project
and the product test strategy, a list of testing deliverables, the plan for development and
evolution of the STP, reference material, and agency definitions and acronyms used in the
STP.
The Software Test Plan (STP) is designed to prescribe the scope, approach, resources,
and schedule of all testing activities. The plan must identify the items to be tested, the
features to be tested, the types of testing to be performed, the personnel responsible for
testing, the resources and schedule required to complete testing, and the risks
associated with the plan.
1.1 Objectives
(Describe, at a high level, the scope, approach, resources, and schedule of the
testing activities. Provide a concise summary of the test plan objectives, the
products to be delivered, major work activities, major work products, major
milestones, required resources, and master high-level schedules, budget, and
effort requirements.)
1.2 Testing Strategy
Testing is the process of analyzing a software item to detect the differences
between existing and required conditions and to evaluate the features of the
software item. (This may appear as a specific document (such as a Test
Specification), or it may be part of the organization's standard test approach. For
each level of testing, there should be a test plan and an appropriate set of
deliverables. The test strategy should be clearly defined and the Software Test
Plan acts as the high-level test plan. Specific testing activities will have their own
test plan. Refer to section 5 of this document for a detailed list of specific test
plans.)
Specific test plan components include:
Software Test Plan
7/21/2013 1:40:54 PM 2
Purpose for this level of test,
Items to be tested,
Features to be tested,
Features not to be tested,
Management and technical approach,
Pass / Fail criteria,
Individual roles and responsibilities,
Milestones,
Schedules, and
Risk assumptions and constraints.
1.3 Scope
(Specify the plans for producing both scheduled and unscheduled updates to the
Software Test Plan (change management). Methods for distribution of updates
shall be specified along with version control and configuration management
requirements must be defined.)
Testing will be performed at several points in the life cycle as the product is
constructed. Testing is a very 'dependent' activity. As a result, test planning
is a continuing activity performed throughout the system development life
cycle. Test plans must be developed for each level of product testing.
1.4 Reference Material
(Provide a complete list of all documents and other sources referenced in the
Software Test Plan. Reference to the following documents (when they exist) is
required for the high-level test plan:
Project authorization,
Project plan,
Quality assurance plan,
Configuration management plan,
Organization policies and procedures, and
Relevant standards.)
1.5 Definitions and Acronyms
(Specify definitions of all terms and agency acronyms required to properly
Software Test Plan
7/21/2013 1:40:54 PM 3
interpret the Software Test Plan. Reference may be made to the Glossary of Terms
on the IRMC web page.)
2. TEST ITEMS
(Specify the test items included in the plan. Supply references to the following item
documentation:
Requirements specification,
Design specification,
Users guide,
Operations guide,
Installation guide,
Features (availability, response time),
Defect removal procedures, and
Verification and validation plans.)
2.1 Program Modules
(Outline testing to be performed by the developer for each module being
built.)
2.2 Job Control Procedures
(Describe testing to be performed on job control language (JCL), production
scheduling and control, calls, and job sequencing.)
2.3 User Procedures
(Describe the testing to be performed on all user documentation to ensure that
it is correct, complete, and comprehensive.)
2.4 Operator Procedures
(Describe the testing procedures to ensure that the application can be run and
supported in a production environment (include Help Desk procedures)).
Software Test Plan
7/21/2013 1:40:54 PM 4
3. FEATURES TO BE TESTED
(Identify all software features and combinations of software features to be tested. Identify the
test design specifications associated with each feature and each combination of features.)
4. FEATURES NOT TO BE TESTED
(Identify all features and specific combinations of features that will not be tested along with
the reasons.)
5. APPROACH
(Describe the overall approaches to testing. The approach should be described in sufficient
detail to permit identification of the major testing tasks and estimation of the time required to
do each task. Identify the types of testing to be performed along with the methods and criteria
to be used in performing test activities. Describe the specific methods and procedures for
each type of testing. Define the detailed criteria for evaluating the test results.)
(For each level of testing there should be a test plan and the appropriate set of deliverables.
Identify the inputs required for each type of test. Specify the source of the input. Also, identify
the outputs from each type of testing and specify the purpose and format for each test output.
Specify the minimum degree of comprehensiveness desired. Identify the techniques that will
be used to judge the comprehensiveness of the testing effort. Specify any additional
completion criteria (e.g., error frequency). The techniques to be used to trace requirements
should also be specified.)
5.1 Component Testing
(Testing conducted to verify the implementation of the design for one software
element (e.g., unit, module) or a collection of software elements. Sometimes called
unit testing. The purpose of component testing is to ensure that the program logic
is complete and correct and ensuring that the component works as designed.)
5.2 Integration Testing
(Testing conducted in which software elements, hardware elements, or both are
combined and tested until the entire system has been integrated. The purpose of
integration testing is to ensure that design objectives are met and ensures that the
software, as a complete entity, complies with operational requirements.
Software Test Plan
7/21/2013 1:40:54 PM 5
Integration testing is also called System Testing.)
5.3 Conversion Testing
(Testing to ensure that all data elements and historical data is converted from an
old system format to the new system format.)
5.4 Job Stream Testing
(Testing to ensure that the application operates in the production environment.)
5.5 Interface Testing
(Testing done to ensure that the application operates efficiently and effectively
outside the application boundary with all interface systems.)
5.6 Security Testing
(Testing done to ensure that the application systems control and auditability
features of the application are functional.)
5.7 Recovery Testing
(Testing done to ensure that application restart and backup and recovery facilities
operate as designed.)
5.8 Performance Testing
(Testing done to ensure that that the application performs to customer
expectations (response time, availability, portability, and scalability)).
5.9 Regression Testing
(Testing done to ensure that that applied changes to the application have not
adversely affected previously tested functionality.)
5.10 Acceptance Testing
(Testing conducted to determine whether or not a system satisfies the acceptance
criteria and to enable the customer to determine whether or not to accept the
Software Test Plan
7/21/2013 1:40:54 PM 6
system. Acceptance testing ensures that customer requirements' objectives are met
and that all components are correctly included in a customer package.)
5.11 Beta Testing
(Testing, done by the customer, using a pre-release version of the product to
verify and validate that the system meets business functional requirements. The
purpose of beta testing is to detect application faults, failures, and defects.)
6. PASS / FAIL CRITERIA
(Specify the criteria to be used to determine whether each item has passed or failed
testing.)
6.1 Suspension Criteria
(Specify the criteria used to suspend all or a portion of the testing activity on test
items associated with the plan.)
6.2 Resumption Criteria
(Specify the conditions that need to be met to resume testing activities after
suspension. Specify the test items that must be repeated when testing is resumed.)
6.3 Approval Criteria
(Specify the conditions that need to be met to approve test results. Define the
formal testing approval process.)
7. TESTING PROCESS
(Identify the methods and criteria used in performing test activities. Define the specific
methods and procedures for each type of test. Define the detailed criteria for evaluating
test results.)
7.1 Test Deliverables
(Identify the deliverable documents from the test process. Test input and output
data should be identified as deliverables. Testing report logs, test incident
reports, test summary reports, and metrics' reports must be considered testing
deliverables.)
7.2 Testing Tasks
Software Test Plan
7/21/2013 1:40:54 PM 7
(Identify the set of tasks necessary to prepare for and perform testing activities.
Identify all intertask dependencies and any specific skills required.)
7.3 Responsibilities
(Identify the groups responsible for managing, designing, preparing, executing,
witnessing, checking, and resolving test activities. These groups may include the
developers, testers, operations staff, technical support staff, data administration
staff, and the user staff.)
7.4 Resources
(Identify the resources allocated for the performance of testing tasks. Identify the
organizational elements or individuals responsible for performing testing
activities. Assign specific responsibilities. Specify resources by category. If
automated tools are to be used in testing, specify the source of the tools,
availability, and the usage requirements.)
7.5 Schedule
(Identify the high level schedule for each testing task. Establish specific
milestones for initiating and completing each type of test activity, for the
development of a comprehensive plan, for the receipt of each test input, and for
the delivery of test output. Estimate the time required to do each test activity.)
(When planning and scheduling testing activities, it must be recognized that the
testing process is iterative based on the testing task dependencies.)
8. ENVIRONMENTAL REQUIREMENTS
(Specify both the necessary and desired properties of the test environment including the
physical characteristics, communications, mode of usage, and testing supplies. Also provide
the levels of security required to perform test activities. Identify special test tools needed and
other testing needs (space, machine time, and stationary supplies. Identify the source of all
needs that is not currently available to the test group.)
8.1 Hardware
(Identify the computer hardware and network requirements needed to complete
test activities.)
8.2 Software
(Identify the software requirements needed to complete testing activities.)
Software Test Plan
7/21/2013 1:40:54 PM 8
8.3 Security
(Identify the testing environment security and asset protection requirements.)
8.4 Tools
(Identify the special software tools, techniques, and methodologies employed in
the testing efforts. The purpose and use of each tool shall be described. Plans for
the acquisition, training, support, and qualification for each tool or technique.)
8.5 Publications
(Identify the documents and publications that are required to support testing
activities.)
8.6 Risks and Assumptions
(Identify significant constraints on testing such as test item availability, test
resource availability, and time constraints. Identify the risks and assumptions
associated with testing tasks including schedule, resources, approach and
documentation. Specify a contingency plan for each risk factor.)
9. CHANGE MANAGEMENT PROCEDURES
(Identify the software test plan change management process. Define the change initiation,
change review, and change authorization process.)
10. PLAN APPROVALS
(Identify the plan approvers. List the name, signature and date of plan approval.)

More Related Content

What's hot

02 software test plan template
02 software test plan template02 software test plan template
02 software test plan templateAndrei Hortúa
 
Sw Software QA Testing
Sw Software QA TestingSw Software QA Testing
Sw Software QA Testingjonathan077070
 
Test Plan Template
Test Plan TemplateTest Plan Template
Test Plan TemplateH2Kinfosys
 
Testing throughout the software life cycle & statistic techniques
Testing throughout the software life cycle & statistic techniquesTesting throughout the software life cycle & statistic techniques
Testing throughout the software life cycle & statistic techniquesYAObbiIkhsan
 
sample-test-plan-template.pdf
sample-test-plan-template.pdfsample-test-plan-template.pdf
sample-test-plan-template.pdfempite
 
SOFTWARE MEASUREMENT A PROCESS MODEL
SOFTWARE MEASUREMENT A PROCESS MODELSOFTWARE MEASUREMENT A PROCESS MODEL
SOFTWARE MEASUREMENT A PROCESS MODELAmin Bandeali
 
Testing throughout the software life cycle & statistic techniques
Testing throughout the software life cycle & statistic techniquesTesting throughout the software life cycle & statistic techniques
Testing throughout the software life cycle & statistic techniquesNovika Damai Yanti
 
Unit II Software Testing and Quality Assurance
Unit II Software Testing and Quality AssuranceUnit II Software Testing and Quality Assurance
Unit II Software Testing and Quality AssuranceVinothkumaR Ramu
 
Test Planning and Test Estimation Techniques
Test Planning and Test Estimation TechniquesTest Planning and Test Estimation Techniques
Test Planning and Test Estimation TechniquesMurageppa-QA
 
Chapter 4 - Performance Testing Tasks
Chapter 4 - Performance Testing TasksChapter 4 - Performance Testing Tasks
Chapter 4 - Performance Testing TasksNeeraj Kumar Singh
 
03 software test-plan-template
03 software test-plan-template03 software test-plan-template
03 software test-plan-templateAndrei Hortúa
 

What's hot (20)

02 software test plan template
02 software test plan template02 software test plan template
02 software test plan template
 
Sw Software QA Testing
Sw Software QA TestingSw Software QA Testing
Sw Software QA Testing
 
CTFL chapter 06
CTFL chapter 06CTFL chapter 06
CTFL chapter 06
 
Test Plan Template
Test Plan TemplateTest Plan Template
Test Plan Template
 
Testing throughout the software life cycle & statistic techniques
Testing throughout the software life cycle & statistic techniquesTesting throughout the software life cycle & statistic techniques
Testing throughout the software life cycle & statistic techniques
 
CTFL chapter 05
CTFL chapter 05CTFL chapter 05
CTFL chapter 05
 
sample-test-plan-template.pdf
sample-test-plan-template.pdfsample-test-plan-template.pdf
sample-test-plan-template.pdf
 
Chapter 3 - Reviews
Chapter 3 - ReviewsChapter 3 - Reviews
Chapter 3 - Reviews
 
SOFTWARE MEASUREMENT A PROCESS MODEL
SOFTWARE MEASUREMENT A PROCESS MODELSOFTWARE MEASUREMENT A PROCESS MODEL
SOFTWARE MEASUREMENT A PROCESS MODEL
 
Test plan
Test planTest plan
Test plan
 
Testing throughout the software life cycle & statistic techniques
Testing throughout the software life cycle & statistic techniquesTesting throughout the software life cycle & statistic techniques
Testing throughout the software life cycle & statistic techniques
 
Unit II Software Testing and Quality Assurance
Unit II Software Testing and Quality AssuranceUnit II Software Testing and Quality Assurance
Unit II Software Testing and Quality Assurance
 
Test Planning and Test Estimation Techniques
Test Planning and Test Estimation TechniquesTest Planning and Test Estimation Techniques
Test Planning and Test Estimation Techniques
 
Chapter 4 - Performance Testing Tasks
Chapter 4 - Performance Testing TasksChapter 4 - Performance Testing Tasks
Chapter 4 - Performance Testing Tasks
 
Astqb Slayb
Astqb SlaybAstqb Slayb
Astqb Slayb
 
Test Life Cycle
Test Life CycleTest Life Cycle
Test Life Cycle
 
Test plan
Test planTest plan
Test plan
 
Test planoutline
Test planoutlineTest planoutline
Test planoutline
 
03 software test-plan-template
03 software test-plan-template03 software test-plan-template
03 software test-plan-template
 
Qa documentation pp
Qa documentation ppQa documentation pp
Qa documentation pp
 

Viewers also liked

Rahvastikupüramiid konspekt
Rahvastikupüramiid   konspektRahvastikupüramiid   konspekt
Rahvastikupüramiid konspektSille Tekku
 
Driving Out Of Control
Driving Out Of ControlDriving Out Of Control
Driving Out Of Controlslovejoy
 
Scrap Your MapReduce - Apache Spark
 Scrap Your MapReduce - Apache Spark Scrap Your MapReduce - Apache Spark
Scrap Your MapReduce - Apache SparkIndicThreads
 
1 u1 conceptos_basicoscalidadsoftware
1 u1 conceptos_basicoscalidadsoftware1 u1 conceptos_basicoscalidadsoftware
1 u1 conceptos_basicoscalidadsoftwareAndrei Hortúa
 
требования к кандидатом в крупные It компании
требования к кандидатом в крупные It компаниитребования к кандидатом в крупные It компании
требования к кандидатом в крупные It компанииНиколай Голтвенко
 
Agile Load Testing In The Real World
Agile Load Testing In The Real WorldAgile Load Testing In The Real World
Agile Load Testing In The Real WorldSOASTA
 
Testing check list
Testing check listTesting check list
Testing check listAtul Pant
 
Bank_Automated_API_Testing
Bank_Automated_API_TestingBank_Automated_API_Testing
Bank_Automated_API_TestingAndy Saunders
 

Viewers also liked (13)

Kultuur 1997-2007 / Culture 1997-2007
Kultuur 1997-2007 / Culture 1997-2007Kultuur 1997-2007 / Culture 1997-2007
Kultuur 1997-2007 / Culture 1997-2007
 
Diana Beltadze: REL 2011: rahvus, kodakondsus, emakeel
Diana Beltadze: REL 2011: rahvus, kodakondsus, emakeelDiana Beltadze: REL 2011: rahvus, kodakondsus, emakeel
Diana Beltadze: REL 2011: rahvus, kodakondsus, emakeel
 
Rahvastikupüramiid konspekt
Rahvastikupüramiid   konspektRahvastikupüramiid   konspekt
Rahvastikupüramiid konspekt
 
Geograafia
GeograafiaGeograafia
Geograafia
 
Siim Krusell: Eesti elu arvudes 2012. aastal
Siim Krusell: Eesti elu arvudes 2012. aastalSiim Krusell: Eesti elu arvudes 2012. aastal
Siim Krusell: Eesti elu arvudes 2012. aastal
 
Driving Out Of Control
Driving Out Of ControlDriving Out Of Control
Driving Out Of Control
 
Scrap Your MapReduce - Apache Spark
 Scrap Your MapReduce - Apache Spark Scrap Your MapReduce - Apache Spark
Scrap Your MapReduce - Apache Spark
 
1 u1 conceptos_basicoscalidadsoftware
1 u1 conceptos_basicoscalidadsoftware1 u1 conceptos_basicoscalidadsoftware
1 u1 conceptos_basicoscalidadsoftware
 
требования к кандидатом в крупные It компании
требования к кандидатом в крупные It компаниитребования к кандидатом в крупные It компании
требования к кандидатом в крупные It компании
 
Scrum in five minutes
Scrum in five minutesScrum in five minutes
Scrum in five minutes
 
Agile Load Testing In The Real World
Agile Load Testing In The Real WorldAgile Load Testing In The Real World
Agile Load Testing In The Real World
 
Testing check list
Testing check listTesting check list
Testing check list
 
Bank_Automated_API_Testing
Bank_Automated_API_TestingBank_Automated_API_Testing
Bank_Automated_API_Testing
 

Similar to Testplan (20)

Test plan on iit website
Test plan on iit websiteTest plan on iit website
Test plan on iit website
 
Testing software development
Testing software developmentTesting software development
Testing software development
 
Test planning
Test planningTest planning
Test planning
 
manual-testing
manual-testingmanual-testing
manual-testing
 
T0 numtq0nje=
T0 numtq0nje=T0 numtq0nje=
T0 numtq0nje=
 
Software Testing and Quality Assurance Assignment 3
Software Testing and Quality Assurance Assignment 3Software Testing and Quality Assurance Assignment 3
Software Testing and Quality Assurance Assignment 3
 
Testing Standards List
Testing Standards ListTesting Standards List
Testing Standards List
 
Testing throughout the software life cycle
Testing throughout the software life cycleTesting throughout the software life cycle
Testing throughout the software life cycle
 
Sample test-plan-template
Sample test-plan-templateSample test-plan-template
Sample test-plan-template
 
software testing strategies
software testing strategiessoftware testing strategies
software testing strategies
 
SDET UNIT 3.pptx
SDET UNIT 3.pptxSDET UNIT 3.pptx
SDET UNIT 3.pptx
 
Quality Assurance Process
Quality Assurance ProcessQuality Assurance Process
Quality Assurance Process
 
Unit 3 for st
Unit 3 for stUnit 3 for st
Unit 3 for st
 
stlc
stlcstlc
stlc
 
Manual Testing Interview Questions & Answers.docx
Manual Testing Interview Questions & Answers.docxManual Testing Interview Questions & Answers.docx
Manual Testing Interview Questions & Answers.docx
 
38475471 qa-and-software-testing-interview-questions-and-answers
38475471 qa-and-software-testing-interview-questions-and-answers38475471 qa-and-software-testing-interview-questions-and-answers
38475471 qa-and-software-testing-interview-questions-and-answers
 
STLC-ppt-1.pptx
STLC-ppt-1.pptxSTLC-ppt-1.pptx
STLC-ppt-1.pptx
 
stlc
stlcstlc
stlc
 
QACampus PPT (STLC)
QACampus PPT (STLC)QACampus PPT (STLC)
QACampus PPT (STLC)
 
SOFTWARE TESTING
SOFTWARE TESTINGSOFTWARE TESTING
SOFTWARE TESTING
 

More from Andrei Hortúa

Conceptos basicos de programacion con pl sql
Conceptos basicos de programacion con pl sqlConceptos basicos de programacion con pl sql
Conceptos basicos de programacion con pl sqlAndrei Hortúa
 
Libro cambio climatico
Libro cambio climaticoLibro cambio climatico
Libro cambio climaticoAndrei Hortúa
 
1 u4 ciclo_devidacalidad
1 u4 ciclo_devidacalidad1 u4 ciclo_devidacalidad
1 u4 ciclo_devidacalidadAndrei Hortúa
 
1 u3 aseguramiento_calidadsoftware
1 u3 aseguramiento_calidadsoftware1 u3 aseguramiento_calidadsoftware
1 u3 aseguramiento_calidadsoftwareAndrei Hortúa
 
1 u2 calidad_productoproceso
1 u2 calidad_productoproceso1 u2 calidad_productoproceso
1 u2 calidad_productoprocesoAndrei Hortúa
 
7 habitos de la gente altamente efectiva
7 habitos de la gente altamente efectiva7 habitos de la gente altamente efectiva
7 habitos de la gente altamente efectivaAndrei Hortúa
 
Relaciones en el entorno de trabajo
Relaciones en el entorno de trabajoRelaciones en el entorno de trabajo
Relaciones en el entorno de trabajoAndrei Hortúa
 
MIT SOFTWARE TEST PLAN
MIT SOFTWARE TEST PLANMIT SOFTWARE TEST PLAN
MIT SOFTWARE TEST PLANAndrei Hortúa
 
Automated testing handbook
Automated testing handbookAutomated testing handbook
Automated testing handbookAndrei Hortúa
 
quality-assurance_best_practice_guide_4 0
quality-assurance_best_practice_guide_4 0quality-assurance_best_practice_guide_4 0
quality-assurance_best_practice_guide_4 0Andrei Hortúa
 
The project gutenberg e book of welsh fairy tales, by william elliot griffis
The project gutenberg e book of welsh fairy tales, by william elliot griffisThe project gutenberg e book of welsh fairy tales, by william elliot griffis
The project gutenberg e book of welsh fairy tales, by william elliot griffisAndrei Hortúa
 
The project gutenberg e book, english fairy tales, by flora annie steel
The project gutenberg e book, english fairy tales, by flora annie steelThe project gutenberg e book, english fairy tales, by flora annie steel
The project gutenberg e book, english fairy tales, by flora annie steelAndrei Hortúa
 
The project gutenberg e book, fairy tales from brazil, by elsie spicer
The project gutenberg e book, fairy tales from brazil, by elsie spicerThe project gutenberg e book, fairy tales from brazil, by elsie spicer
The project gutenberg e book, fairy tales from brazil, by elsie spicerAndrei Hortúa
 
The project gutenberg e book of aesop's fables, by aesop
The project gutenberg e book of aesop's fables, by aesopThe project gutenberg e book of aesop's fables, by aesop
The project gutenberg e book of aesop's fables, by aesopAndrei Hortúa
 
The project gutenberg e book, fairy tales every child should know
The project gutenberg e book, fairy tales every child should knowThe project gutenberg e book, fairy tales every child should know
The project gutenberg e book, fairy tales every child should knowAndrei Hortúa
 

More from Andrei Hortúa (20)

Conceptos basicos de programacion con pl sql
Conceptos basicos de programacion con pl sqlConceptos basicos de programacion con pl sql
Conceptos basicos de programacion con pl sql
 
Diagramas uml
Diagramas umlDiagramas uml
Diagramas uml
 
Libro cambio climatico
Libro cambio climaticoLibro cambio climatico
Libro cambio climatico
 
1 u4 ciclo_devidacalidad
1 u4 ciclo_devidacalidad1 u4 ciclo_devidacalidad
1 u4 ciclo_devidacalidad
 
1 u3 aseguramiento_calidadsoftware
1 u3 aseguramiento_calidadsoftware1 u3 aseguramiento_calidadsoftware
1 u3 aseguramiento_calidadsoftware
 
1 u2 calidad_productoproceso
1 u2 calidad_productoproceso1 u2 calidad_productoproceso
1 u2 calidad_productoproceso
 
7 habitos de la gente altamente efectiva
7 habitos de la gente altamente efectiva7 habitos de la gente altamente efectiva
7 habitos de la gente altamente efectiva
 
Ielts handbook 2007
Ielts handbook 2007Ielts handbook 2007
Ielts handbook 2007
 
Daisy World Theory
Daisy World TheoryDaisy World Theory
Daisy World Theory
 
Relaciones en el entorno de trabajo
Relaciones en el entorno de trabajoRelaciones en el entorno de trabajo
Relaciones en el entorno de trabajo
 
Phrasal verbs
Phrasal verbsPhrasal verbs
Phrasal verbs
 
MIT SOFTWARE TEST PLAN
MIT SOFTWARE TEST PLANMIT SOFTWARE TEST PLAN
MIT SOFTWARE TEST PLAN
 
Automated testing handbook
Automated testing handbookAutomated testing handbook
Automated testing handbook
 
quality-assurance_best_practice_guide_4 0
quality-assurance_best_practice_guide_4 0quality-assurance_best_practice_guide_4 0
quality-assurance_best_practice_guide_4 0
 
The project gutenberg e book of welsh fairy tales, by william elliot griffis
The project gutenberg e book of welsh fairy tales, by william elliot griffisThe project gutenberg e book of welsh fairy tales, by william elliot griffis
The project gutenberg e book of welsh fairy tales, by william elliot griffis
 
The project gutenberg e book, english fairy tales, by flora annie steel
The project gutenberg e book, english fairy tales, by flora annie steelThe project gutenberg e book, english fairy tales, by flora annie steel
The project gutenberg e book, english fairy tales, by flora annie steel
 
The project gutenberg e book, fairy tales from brazil, by elsie spicer
The project gutenberg e book, fairy tales from brazil, by elsie spicerThe project gutenberg e book, fairy tales from brazil, by elsie spicer
The project gutenberg e book, fairy tales from brazil, by elsie spicer
 
Hamlet l404807
Hamlet l404807Hamlet l404807
Hamlet l404807
 
The project gutenberg e book of aesop's fables, by aesop
The project gutenberg e book of aesop's fables, by aesopThe project gutenberg e book of aesop's fables, by aesop
The project gutenberg e book of aesop's fables, by aesop
 
The project gutenberg e book, fairy tales every child should know
The project gutenberg e book, fairy tales every child should knowThe project gutenberg e book, fairy tales every child should know
The project gutenberg e book, fairy tales every child should know
 

Recently uploaded

Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Will Schroeder
 
AI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity WebinarAI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity WebinarPrecisely
 
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostKubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostMatt Ray
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...Aggregage
 
COMPUTER 10: Lesson 7 - File Storage and Online Collaboration
COMPUTER 10: Lesson 7 - File Storage and Online CollaborationCOMPUTER 10: Lesson 7 - File Storage and Online Collaboration
COMPUTER 10: Lesson 7 - File Storage and Online Collaborationbruanjhuli
 
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfJamie (Taka) Wang
 
Machine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdfMachine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdfAijun Zhang
 
Nanopower In Semiconductor Industry.pdf
Nanopower  In Semiconductor Industry.pdfNanopower  In Semiconductor Industry.pdf
Nanopower In Semiconductor Industry.pdfPedro Manuel
 
Linked Data in Production: Moving Beyond Ontologies
Linked Data in Production: Moving Beyond OntologiesLinked Data in Production: Moving Beyond Ontologies
Linked Data in Production: Moving Beyond OntologiesDavid Newbury
 
Videogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdfVideogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdfinfogdgmi
 
Crea il tuo assistente AI con lo Stregatto (open source python framework)
Crea il tuo assistente AI con lo Stregatto (open source python framework)Crea il tuo assistente AI con lo Stregatto (open source python framework)
Crea il tuo assistente AI con lo Stregatto (open source python framework)Commit University
 
How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?IES VE
 
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfUiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfDianaGray10
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Adtran
 
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...UbiTrack UK
 
Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1DianaGray10
 
UiPath Community: AI for UiPath Automation Developers
UiPath Community: AI for UiPath Automation DevelopersUiPath Community: AI for UiPath Automation Developers
UiPath Community: AI for UiPath Automation DevelopersUiPathCommunity
 
Building AI-Driven Apps Using Semantic Kernel.pptx
Building AI-Driven Apps Using Semantic Kernel.pptxBuilding AI-Driven Apps Using Semantic Kernel.pptx
Building AI-Driven Apps Using Semantic Kernel.pptxUdaiappa Ramachandran
 
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsIgniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsSafe Software
 

Recently uploaded (20)

Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
 
AI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity WebinarAI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity Webinar
 
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostKubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
 
COMPUTER 10: Lesson 7 - File Storage and Online Collaboration
COMPUTER 10: Lesson 7 - File Storage and Online CollaborationCOMPUTER 10: Lesson 7 - File Storage and Online Collaboration
COMPUTER 10: Lesson 7 - File Storage and Online Collaboration
 
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
 
Machine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdfMachine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdf
 
Nanopower In Semiconductor Industry.pdf
Nanopower  In Semiconductor Industry.pdfNanopower  In Semiconductor Industry.pdf
Nanopower In Semiconductor Industry.pdf
 
Linked Data in Production: Moving Beyond Ontologies
Linked Data in Production: Moving Beyond OntologiesLinked Data in Production: Moving Beyond Ontologies
Linked Data in Production: Moving Beyond Ontologies
 
Videogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdfVideogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdf
 
Crea il tuo assistente AI con lo Stregatto (open source python framework)
Crea il tuo assistente AI con lo Stregatto (open source python framework)Crea il tuo assistente AI con lo Stregatto (open source python framework)
Crea il tuo assistente AI con lo Stregatto (open source python framework)
 
How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?
 
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfUiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™
 
201610817 - edge part1
201610817 - edge part1201610817 - edge part1
201610817 - edge part1
 
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
 
Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1
 
UiPath Community: AI for UiPath Automation Developers
UiPath Community: AI for UiPath Automation DevelopersUiPath Community: AI for UiPath Automation Developers
UiPath Community: AI for UiPath Automation Developers
 
Building AI-Driven Apps Using Semantic Kernel.pptx
Building AI-Driven Apps Using Semantic Kernel.pptxBuilding AI-Driven Apps Using Semantic Kernel.pptx
Building AI-Driven Apps Using Semantic Kernel.pptx
 
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsIgniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
 

Testplan

  • 1. Software Test Plan (STP) Template Items that are intended to stay in as part of your document are in bold; explanatory comments are in italic text. Plain text is used where you might insert wording about your project. This document is an annotated outline for a Software Test Plan, adapted from the IEEE Standard for Software Test Documentation (Std 829-1998). Tailor as appropriate. Where you decide to omit a section, you might keep the header, but insert a comment saying why you omit the element.
  • 3. Agency Name Project Name Software Quality Assurance Plan Version: (n) Date: (mm/dd/yyyy)
  • 4. Document History and Distribution 1. Revision History Revision # Revision Date Description of Change Author 2. Distribution Recipient Name Recipient Organization Distribution Method
  • 5. Software Test Plan 7/21/2013 1:40:54 PM i TABLE OF CONTENTS 1. INTRODUCTION....................................................................................................................................................1 2. TEST ITEMS...........................................................................................................................................................3 3. FEATURES TO BE TESTED ...............................................................................................................................4 4. FEATURES NOT TO BE TESTED......................................................................................................................4 5. APPROACH ............................................................................................................................................................4 6. PASS / FAIL CRITERIA ........................................................................................................................................6 7. TESTING PROCESS.............................................................................................................................................6 8. ENVIRONMENTAL REQUIREMENTS...............................................................................................................7 9. CHANGE MANAGEMENT PROCEDURES.......................................................................................................8 10. PLAN APPROVALS ............................................................................................................................................8
  • 6. Software Test Plan 7/21/2013 1:40:54 PM 1 1. INTRODUCTION (NOTE 1: THE SOFTWARE TEST PLAN GUIDELINES WERE DERIVED AND DEVELOPED FROM IEEE STANDARD FOR SOFTWARE TEST DOCUMENTATION (829-1998)). (Note 2: The ordering of Software Test Plan (STP) elements is not meant to imply that the sections or subsections must be developed or presented in that order. The order of presentation is intended for ease of use, not as a guide to preparing the various elements of the Software Test Plan. If some or all of the content of a section is in another document, then a reference to that material may be listed in place of the corresponding content.) The Introduction section of the Software Test Plan (STP) provides an overview of the project and the product test strategy, a list of testing deliverables, the plan for development and evolution of the STP, reference material, and agency definitions and acronyms used in the STP. The Software Test Plan (STP) is designed to prescribe the scope, approach, resources, and schedule of all testing activities. The plan must identify the items to be tested, the features to be tested, the types of testing to be performed, the personnel responsible for testing, the resources and schedule required to complete testing, and the risks associated with the plan. 1.1 Objectives (Describe, at a high level, the scope, approach, resources, and schedule of the testing activities. Provide a concise summary of the test plan objectives, the products to be delivered, major work activities, major work products, major milestones, required resources, and master high-level schedules, budget, and effort requirements.) 1.2 Testing Strategy Testing is the process of analyzing a software item to detect the differences between existing and required conditions and to evaluate the features of the software item. (This may appear as a specific document (such as a Test Specification), or it may be part of the organization's standard test approach. For each level of testing, there should be a test plan and an appropriate set of deliverables. The test strategy should be clearly defined and the Software Test Plan acts as the high-level test plan. Specific testing activities will have their own test plan. Refer to section 5 of this document for a detailed list of specific test plans.) Specific test plan components include:
  • 7. Software Test Plan 7/21/2013 1:40:54 PM 2 Purpose for this level of test, Items to be tested, Features to be tested, Features not to be tested, Management and technical approach, Pass / Fail criteria, Individual roles and responsibilities, Milestones, Schedules, and Risk assumptions and constraints. 1.3 Scope (Specify the plans for producing both scheduled and unscheduled updates to the Software Test Plan (change management). Methods for distribution of updates shall be specified along with version control and configuration management requirements must be defined.) Testing will be performed at several points in the life cycle as the product is constructed. Testing is a very 'dependent' activity. As a result, test planning is a continuing activity performed throughout the system development life cycle. Test plans must be developed for each level of product testing. 1.4 Reference Material (Provide a complete list of all documents and other sources referenced in the Software Test Plan. Reference to the following documents (when they exist) is required for the high-level test plan: Project authorization, Project plan, Quality assurance plan, Configuration management plan, Organization policies and procedures, and Relevant standards.) 1.5 Definitions and Acronyms (Specify definitions of all terms and agency acronyms required to properly
  • 8. Software Test Plan 7/21/2013 1:40:54 PM 3 interpret the Software Test Plan. Reference may be made to the Glossary of Terms on the IRMC web page.) 2. TEST ITEMS (Specify the test items included in the plan. Supply references to the following item documentation: Requirements specification, Design specification, Users guide, Operations guide, Installation guide, Features (availability, response time), Defect removal procedures, and Verification and validation plans.) 2.1 Program Modules (Outline testing to be performed by the developer for each module being built.) 2.2 Job Control Procedures (Describe testing to be performed on job control language (JCL), production scheduling and control, calls, and job sequencing.) 2.3 User Procedures (Describe the testing to be performed on all user documentation to ensure that it is correct, complete, and comprehensive.) 2.4 Operator Procedures (Describe the testing procedures to ensure that the application can be run and supported in a production environment (include Help Desk procedures)).
  • 9. Software Test Plan 7/21/2013 1:40:54 PM 4 3. FEATURES TO BE TESTED (Identify all software features and combinations of software features to be tested. Identify the test design specifications associated with each feature and each combination of features.) 4. FEATURES NOT TO BE TESTED (Identify all features and specific combinations of features that will not be tested along with the reasons.) 5. APPROACH (Describe the overall approaches to testing. The approach should be described in sufficient detail to permit identification of the major testing tasks and estimation of the time required to do each task. Identify the types of testing to be performed along with the methods and criteria to be used in performing test activities. Describe the specific methods and procedures for each type of testing. Define the detailed criteria for evaluating the test results.) (For each level of testing there should be a test plan and the appropriate set of deliverables. Identify the inputs required for each type of test. Specify the source of the input. Also, identify the outputs from each type of testing and specify the purpose and format for each test output. Specify the minimum degree of comprehensiveness desired. Identify the techniques that will be used to judge the comprehensiveness of the testing effort. Specify any additional completion criteria (e.g., error frequency). The techniques to be used to trace requirements should also be specified.) 5.1 Component Testing (Testing conducted to verify the implementation of the design for one software element (e.g., unit, module) or a collection of software elements. Sometimes called unit testing. The purpose of component testing is to ensure that the program logic is complete and correct and ensuring that the component works as designed.) 5.2 Integration Testing (Testing conducted in which software elements, hardware elements, or both are combined and tested until the entire system has been integrated. The purpose of integration testing is to ensure that design objectives are met and ensures that the software, as a complete entity, complies with operational requirements.
  • 10. Software Test Plan 7/21/2013 1:40:54 PM 5 Integration testing is also called System Testing.) 5.3 Conversion Testing (Testing to ensure that all data elements and historical data is converted from an old system format to the new system format.) 5.4 Job Stream Testing (Testing to ensure that the application operates in the production environment.) 5.5 Interface Testing (Testing done to ensure that the application operates efficiently and effectively outside the application boundary with all interface systems.) 5.6 Security Testing (Testing done to ensure that the application systems control and auditability features of the application are functional.) 5.7 Recovery Testing (Testing done to ensure that application restart and backup and recovery facilities operate as designed.) 5.8 Performance Testing (Testing done to ensure that that the application performs to customer expectations (response time, availability, portability, and scalability)). 5.9 Regression Testing (Testing done to ensure that that applied changes to the application have not adversely affected previously tested functionality.) 5.10 Acceptance Testing (Testing conducted to determine whether or not a system satisfies the acceptance criteria and to enable the customer to determine whether or not to accept the
  • 11. Software Test Plan 7/21/2013 1:40:54 PM 6 system. Acceptance testing ensures that customer requirements' objectives are met and that all components are correctly included in a customer package.) 5.11 Beta Testing (Testing, done by the customer, using a pre-release version of the product to verify and validate that the system meets business functional requirements. The purpose of beta testing is to detect application faults, failures, and defects.) 6. PASS / FAIL CRITERIA (Specify the criteria to be used to determine whether each item has passed or failed testing.) 6.1 Suspension Criteria (Specify the criteria used to suspend all or a portion of the testing activity on test items associated with the plan.) 6.2 Resumption Criteria (Specify the conditions that need to be met to resume testing activities after suspension. Specify the test items that must be repeated when testing is resumed.) 6.3 Approval Criteria (Specify the conditions that need to be met to approve test results. Define the formal testing approval process.) 7. TESTING PROCESS (Identify the methods and criteria used in performing test activities. Define the specific methods and procedures for each type of test. Define the detailed criteria for evaluating test results.) 7.1 Test Deliverables (Identify the deliverable documents from the test process. Test input and output data should be identified as deliverables. Testing report logs, test incident reports, test summary reports, and metrics' reports must be considered testing deliverables.) 7.2 Testing Tasks
  • 12. Software Test Plan 7/21/2013 1:40:54 PM 7 (Identify the set of tasks necessary to prepare for and perform testing activities. Identify all intertask dependencies and any specific skills required.) 7.3 Responsibilities (Identify the groups responsible for managing, designing, preparing, executing, witnessing, checking, and resolving test activities. These groups may include the developers, testers, operations staff, technical support staff, data administration staff, and the user staff.) 7.4 Resources (Identify the resources allocated for the performance of testing tasks. Identify the organizational elements or individuals responsible for performing testing activities. Assign specific responsibilities. Specify resources by category. If automated tools are to be used in testing, specify the source of the tools, availability, and the usage requirements.) 7.5 Schedule (Identify the high level schedule for each testing task. Establish specific milestones for initiating and completing each type of test activity, for the development of a comprehensive plan, for the receipt of each test input, and for the delivery of test output. Estimate the time required to do each test activity.) (When planning and scheduling testing activities, it must be recognized that the testing process is iterative based on the testing task dependencies.) 8. ENVIRONMENTAL REQUIREMENTS (Specify both the necessary and desired properties of the test environment including the physical characteristics, communications, mode of usage, and testing supplies. Also provide the levels of security required to perform test activities. Identify special test tools needed and other testing needs (space, machine time, and stationary supplies. Identify the source of all needs that is not currently available to the test group.) 8.1 Hardware (Identify the computer hardware and network requirements needed to complete test activities.) 8.2 Software (Identify the software requirements needed to complete testing activities.)
  • 13. Software Test Plan 7/21/2013 1:40:54 PM 8 8.3 Security (Identify the testing environment security and asset protection requirements.) 8.4 Tools (Identify the special software tools, techniques, and methodologies employed in the testing efforts. The purpose and use of each tool shall be described. Plans for the acquisition, training, support, and qualification for each tool or technique.) 8.5 Publications (Identify the documents and publications that are required to support testing activities.) 8.6 Risks and Assumptions (Identify significant constraints on testing such as test item availability, test resource availability, and time constraints. Identify the risks and assumptions associated with testing tasks including schedule, resources, approach and documentation. Specify a contingency plan for each risk factor.) 9. CHANGE MANAGEMENT PROCEDURES (Identify the software test plan change management process. Define the change initiation, change review, and change authorization process.) 10. PLAN APPROVALS (Identify the plan approvers. List the name, signature and date of plan approval.)