Software
Testing Life Cycle
They are…
·
Test Planning
·
Test Development
·
Test Execution
·
Result Analysis
·
Bug Tracking
·
Reporting
Plan: -
It is a strategic document, which describes
how to perform a task in an effective, efficient and optimized way.
Test Plan: -
It is a
strategic document, which describes how to perform testing on an application in
an effective, efficient and optimized way.
Optimization: -
Optimization
is a process of utilizing the available input resources to their max and
getting maximum possible output.
 |
1.0 Introduction
1.1
Objective
1.2
Reference Document
2.0 Coverage of Testing
1.0
Features To Be Testing
1.1
Features Not To Be Testing
3.0 Test Strategy
3.1
Levels Of Testing
3.2 Types of
testing
3.3 Test design
techniques
3.4 Configuration
management
3.5 Test metrics
3.6 Terminology
3.7 Automation
Plan
3.8 List of
automated tools
4.0
Base
criteria
4.1 Acceptance
criteria
4.2
Suspension criteria
5.0 Test Deliverable
6.0 Test Environment
7.0 Resource Planning
8.0 Scheduling
9.0 Staffing& Training
10.0 Risks & Contingencies
11.0 Assumptions
12.0 Approval Information
1.0
Introduction: -
1.1 Objective: -
The Purpose
of the document is clearly described here in this section
1.2 Reference
Document: -
The list of
all the documents that are refereed to prepare the test plan will be listed out
her in the section.
2.0
Coverage of Testing: -
2.1
Features to be tested: -
The list of all the features that are to be tested in this phase will be
clearly mentioned here in this section.
2.2
Features not to be tested: -
The list of all the features that are not planned for testing based on
the following criteria will be listed out here in this section
a.
Out of scope features
b.
Low risk features
c. The functionalities that are planned to be incorporated in future
d.
The features that are to be skipped based on the
time constraints.
3.0
Test Strategy: -
Test
strategy is defined as an organizational level term, which is used for testing
all the projects in the organization.
Test Plan: -
It is
defined as a project level term, which is used for testing a particular project
in the organization.
Note: - Test strategy is common for all the projects
but the test plan is specific for a particular project
3.1
Levels of Testing: -
The list of
all the levels of testing that are followed by that company are listed out here
in this section
3.2
Types of Testing: -
The list of
all the types of testing that are followed in that company will be listed out
here in this section.
3.3
Test Design Techniques: -
Technique:
-
Technique is
something i.e., used for accomplishing a complex task in an easy manner.
A
list of all the techniques that are used by that company while developing the
test cases will be listed out here in this section.
Eg: - BVA (Banded value analysis)
ECP
(Equivalence Class Partition)
3.4
Configuration Management:- To be discussed later……
3.5
Test Metrics: -
The list of
all the metrics that are maintained in that company will be listed out here in
this section
3.6
Terminology: -
The list of all the terms and the meaning
that are used in that company will be listed out here in this section
3.7
Automation Plan: -
The list of all the areas that are plan for automation in that company will be listed out here in this section.
3.8
List Of Automated Tools: -
The list of all the automated tools that
are used in that company will be listed out here in this section.
4.0
Base Criteria: -
4.1
Acceptance Criteria: -
When to stop testing feeling that enough
testing has been done on the application is clearly described here in this
section.
4.1
Suspension Criteria: -
When to suspend testing suddenly (abruptly)
will be clearly mentioned here in this section.
5.0
Test Deliverable: -
The list of all the documents that are to
be prepared during the testing phase will be listed out here in this section.
Eg:
Test case, defects profile document.
6.0
Test Environment: -
The customer specified environment would be
clearly described here in this section. The same environment will be simulated
in the company and will be used for testing purpose.
7.0
Resource Planning: -
Who has to do what is clearly described
here in this section.
8.0
Scheduling: -
The starting dates and the ending data of
the each and every tasks is clearly planned here in this section.
9.0
Staffing& Training: -
How much staff is to be recruited and what
kind of training is to be provided is clearly described here in this section.
10.0
Risks & contingencies (Solution Plans): -
The list of all the potential risks and the
corresponding solution plans will be listed out here in this section.
Example:
Risks:
i. Unable to
deliver the software with in deadlines.
ii. Employees may
leave the organization in the middle of the project
iii. Customer may
impose the deadlines.
iv. Unable to test
all the features with in the time.
v. Lack of
expertization
Contingencies
(solution Plans):
i. Proper plan
ensurance.
ii. Employees need
to be maintained on the bench.
iii. What not to be
tested has to be planned in case of imposed dead lines.
iv. Severity &
Priority based testing.
v. Proper
Training needs to be provided.
11.0
Assumptions: -
The list of all the assumptions that are to
be assumed by the test engineer will be listed out here in this section.
12.0 Approval Information: -
Who has to approve what is clearly
described here in this section.
Thank you for sharing such great information very useful to us.
ReplyDeleteSelenium Training in Delhi