Testing in Software Life Cycle

Software Testing Life Cycle(STLC)

Reference:
https://www.guru99.com/software-testing-life-cycle.html
http://www.softwaretestingclass.com/software-testing-life-cycle-stlc
 Software Testing Life Cycle
• Software Testing Life Cycle (STLC) is defined as a sequence
of activities conducted to perform Software Testing.
• It consists of series of activities carried out
methodologically to help certify your software product.
• Each of these stages have a definite Entry and Exit
criteria; , Activities & Deliverables associated with it.
• Entry Criteria: Entry Criteria gives the prerequisite items
that must be completed before testing can begin.
• Exit Criteria: Exit Criteria defines the items that must be
completed before testing can be concluded
 Requirement Traceability Matrix (RTM)

• RTM captures all requirements proposed by the client or software

development team and their traceability in a single document
delivered at the conclusion of the life-cycle.
• In other words, it is a document that maps and traces user
requirement with test cases.
• The main purpose of RTM is to see that all test cases are covered so
that no functionality should miss while doing Software testing.
Why RTM is Important?
• The main agenda of every tester should be to understand the
client’s requirement and make sure that the output product should
be defect-free. To achieve this goal, every QA should understand the
requirement thoroughly and create positive and negative test cases.
RTM Example
Other parameters in RTM
 RTM Can
• Show the requirement coverage in the number
of test cases
• Design status as well as execution status for the
specific test case
• If there is any User Acceptance Test to be done
by the users, then UAT status can also be
captured in the same matrix.
• The related defects and the current state can
also be mentioned in the same matrix.
 STLC Phases
STLC Stage Entry Criteria Activity Exit Criteria Deliverables
Requirement Requirements Analyze business functionality to know the Signed off RTM RTM
Analysis Document business modules and module specific
available (both functionalities. Test automation Automation
functional and non feasibility report feasibility
functional) Identify all transactions in the modules. signed off by the report (if
client applicable
Acceptance Identify all the user profiles.
criteria defined.   
Gather user interface/ authentication,
Application geographic spread requirements.
architectural
document Identify types of tests to be performed.
available.
Gather details about testing priorities and
focus.

Prepare Requirement Traceability Matrix 

(RTM).

Identify test environment details where

testing is supposed to be carried out.

Automation feasibility analysis (if required).

 STLC Phases
STLC Stage Entry Criteria Activity Exit Criteria Deliverables
Test Requirements Analyze various testing approaches Approved test Test
Planning Documents available plan/strategy plan/strategy
document. document.
Requirement Finalize on the best-suited approach
Traceability Effort estimationEffort
matrix. Preparation of test plan/strategy document estimation
document for various types of testing signed off.   document.  
Test automation
feasibility Test tool selection
document.
Test effort estimation

Resource planning and determining

roles and responsibilities.
 STLC Phases
STLC Stage Entry Criteria Activity Exit Criteria Deliverables
Test case Requirements Create test cases, test design, Reviewed and Test
developmen Documents automation scripts (where applicable) signed test cases/scripts
t Cases/scripts
RTM and test Review and baseline test cases and Test data 
plan scripts Reviewed and
signed test data  
Automation Create test data
analysis report
 STLC Phases
STLC Stage Entry Criteria Activity Exit Criteria Deliverables
Test System Design Understand the required architecture, Environment Environment
Environment and architecture environment set-up setup is ready with
setup documents are working as per test data set
available Prepare hardware and software the plan and up
development requirement list checklist
Environment Smoke Test
set-up plan is Finalize connectivity requirements Test data setup Results.
available is complete
Prepare environment setup checklist
Smoke test is
Setup test Environment and test data successful  
Perform smoke test on the build
Accept/reject the build depending on
smoke test result
 STLC Phases
STLC Stage Entry Criteria Activity Exit Criteria Deliverables
Test Cycle Testing has been Evaluate cycle completion criteria based Test Closure Test Closure
closure completed on - Time, Test coverage, Cost, Software report signed report
Quality, Critical Business Objectives off by client
Test results are Test metrics
available Prepare test metrics based on the above
parameters.
Defect logs are
available Document the learning out of the
project
Prepare Test closure report
Qualitative and quantitative reporting of
quality of the work product to the
customer.

Test result analysis to find out the defect

distribution by type and severity
 STLC Phases
STLC Stage Entry Criteria Activity Exit Criteria Deliverables
Test Baselined RTM,  Execute tests as per plan All tests Completed
Execution Test Plan , Test planned are RTM with
case/scripts are Document test results, and log defects executed execution
available for failed cases status
Defects logged
Test Update test plans/test cases, if and tracked to Test cases
environment is necessary closure   updated with
ready results
Map defects to test cases in RTM
Test data set up Defect
is done Retest the defect fixes reports
Unit/Integration Regression Testing of application
test report for
the build to be Track the defects to closure  
tested is
available
 V Model
• The V-model is a type of SDLC model where
process executes in a sequential manner in V-
shape.
• Each phase must be completed before the
next phase begins.
• Testing of the phase is planned in parallel with
corresponding phase of development in V
model.
 V Model

• The V-Model is a unique, linear development

methodology used during a SDLC.
• V model is also known as Verification and
Validation model. In V model, the testing
phase goes in parallel with the development
phase. Thus, the testing phase starts right at
the beginning of SDLC.
 V-Model
Developers Life Cycle Tester’s Life Cycle
(Verification) (Validation)
 Verification & Validation
Verification Validation

Verification addresses the concern: "Are Validation addresses the concern: "Are
you building it right?" you building the right thing?"

Ensures that the software system meets Ensures that the functionalities meet the
all the functionality. Proposed behavior.

Verification takes place first and includes Validation occurs after verification and
the checking for documentation, code, mainly involves the checking of the
etc. overall product.

Done by developers. Done by testers.

It has static activities, as it includes It has dynamic activities, as it includes

collecting reviews, walkthroughs, and executing the software against the
inspections to verify a software. requirements.
 V Model
• Typical V-model shows Software Development activities on
the Left hand side of model and the Right hand side of the
model actual Testing Phases can be performed.
• In this process “Do-Procedure” would be followed by the
developer team and the “Check-Procedure” would be
followed by the testing team to meets the mentioned
requirements.
• The V-model typically consist of the following phases:
1. Unit Testing: Preparation of Unit Test Cases
2. Integration Testing: Preparation of Integration Test Cases
3. System Testing: Preparation of System test cases
4. Acceptance Testing: Preparation of Acceptance Test Cases
 V-Model
• Requirements definition
The needs and requirements of the customer or the future system
user are gathered, specified, and approved. Thus, the purpose of
the system and the desired characteristics are defined.
->The test plan focuses on meeting the functionality specified in
the requirements gathering.
• Functional System Design/System Design
This step maps requirements onto functions and dialogues of the
new system. It’s the phase where system engineers analyze and
understand the business of the proposed system by studying the
user requirements document. They figure out possibilities and
techniques by which the user requirements can be implemented. If
any of the requirements are not feasible, the user is informed of
the issue. 
 V-Model
• Technical/High level system design:
This step designs the implementation of the system. This
includes the definition of interfaces to the system environment
and decomposing the system into smaller, understandable
subsystems (system architecture). Each subsystem can then be
developed as independently as possible.
• Component/Low Level specification:
This step defines each subsystem, including its task, behavior,
inner structure, and interfaces to other subsystems.
• Programming:
Each specified component (module, unit, class) is coded in a
programming language.
V Model Basic Idea/Characteristics
• Implementation and testing activities are
separated but are equally important (left side /
right side).
• The V illustrates the testing aspects of
verification and validation.
• We distinguish between different test levels,
where each test level is testing “against” its
corresponding development level.
 V-Model Advantages
• Each phase of development is tested before moving
to next phase, hence there is higher rate of success.
• It avoids down word flow of defects because each
phase is verified explicitly.
• The model has clear and defined steps. So, it is
easier to implement.
• It is suitable for smaller projects where
requirements are easily understood and fixed.
• It saves a lot of time.
 Disadvantages of V-Model
• The testing team starts in parallel with development. Hence, the overall
budget and resource usage increases.
• Change in requirement are difficult to incorporate. Because if any
changes happens, then the test requirement document must be
updated.
• Guessing the error in the beginning of the project could take more time.
• The working model of the software is only available in the later phases
of the development.
• It is not suitable for complex and large applications because of its rigid
process.
 When to use the V-model?
• The V-shaped model should be used for small to medium sized
projects where requirements are clearly defined and fixed.
• V Model should be followed for the project where very less
probability to make the changes in the middle of testing or
development phase which are unplanned.
• The V-Shaped model should be chosen when sufficient technical
resources are available with needed technical expertise.
• High confidence of customer is required for choosing the V-
Shaped model approach. Since, no prototypes are produced,
there is a very high risk involved in meeting customer
expectations.