SlideShare a Scribd company logo
1 of 50
UNIT 3
SOFTWARE TESTING LIFE
CYCLE
Dr. Pallawi Bulakh
contents
 3.1 Test Planning
 3.2 Test Plan
 3.3 What is a test Plan
 3.4 Who creates a Test Plan
 3.5 When is the Test Plan created
 3.6 Purpose of creating a Test Plan
 3.7 Components of a Test plan.
 3.8 Test design
 3.9 Test implementation and Execution
 3.10 Defect Reporting and tracking
 3.11 Defect life cycle
 3.12 Test closures
 3.13 Test metrics
STLC
 The Software Testing Life Cycle (STLC) is a
systematic approach to testing a software
application to ensure that it meets the
requirements and is free of defects. It is a process
that follows a series of steps or phases, and each
phase has specific objectives and deliverables.
 The STLC is used to ensure that the software is of
high quality, reliable, and meets the needs of the
end-users.
STLC
 The main goal of the STLC is to identify and
document any defects or issues in the
software application as early as possible in the
development process.
 This allows for issues to be addressed and
resolved before the software is released to the
public.
Characteristics of STLC
 STLC is a fundamental part of the Software
Development Life Cycle (SDLC) but STLC
consists of only the testing phases.
 STLC starts as soon as requirements are
defined or software requirement document is
shared by stakeholders.
 STLC yields a step-by-step process to ensure
quality software.
Phases of STLC
1. Requirement Analysis
 Requirement Analysis is the first step of the
Software Testing Life Cycle (STLC).
 In this phase quality assurance team
understands the requirements like what is to
be tested.
 If anything is missing or not understandable
then the quality assurance team meets with
the stakeholders to better understand the
detailed knowledge of requirements.
The activities during the
Requirement Analysis stage :
 Reviewing the software requirements
document (SRD) and other related documents
 Interviewing stakeholders to gather additional
information
 Identifying any ambiguities or inconsistencies
in the requirements
 Identifying any missing or incomplete
requirements
 Identifying any potential risks or issues that
may impact the testing process
2. Test Planning:
 Test Planning is the most efficient phase of the
software testing life cycle where all testing
plans are defined.
 In this phase manager of the testing, team
calculates the estimated effort and cost for the
testing work.
 This phase gets started once the requirement-
gathering phase is completed.
The activities during the Test
Planning stage
 Identifying the testing objectives and scope
 Developing a test strategy: selecting the testing
methods and techniques that will be used
 Identifying the testing environment and resources
needed
 Identifying the test cases that will be executed and
the test data that will be used
 Estimating the time and cost required for testing
 Identifying the test deliverables and milestones
 Assigning roles and responsibilities to the testing
team
 Reviewing and approving the test plan
Test Case Development:
 The test case development phase gets started
once the test planning phase is completed.
 In this phase testing team notes down the
detailed test cases.
 The testing team also prepares the required
test data for the testing.
 When the test cases are prepared then they
are reviewed by the quality assurance team.
The activities during the Test
Case Development stage :
 Identifying the test cases that will be
developed
 Writing test cases that are clear, concise, and
easy to understand
 Creating test data and test scenarios that will
be used in the test cases
 Identifying the expected results for each test
case
 Reviewing and validating the test cases
 Updating the requirement traceability matrix
(RTM) to map requirements to test cases.
4.Test Environment Setup
 Test environment setup is a vital part of the
STLC. Basically, the test environment decides
the conditions on which software is tested.
 This is independent activity and can be started
along with test case development.
 In this process, the testing team is not
involved. either the developer or the customer
creates the testing environment.
5. Test Execution:
 After the test case development and test
environment setup test execution phase gets
started.
 In this phase testing team starts executing test
cases based on prepared test cases in the
earlier step.
The activities during the test
execution stage
 Test execution: The test cases and scripts
created in the test design stage are run against
the software application to identify any defects or
issues.
 Defect logging: Any defects or issues that are
found during test execution are logged in a defect
tracking system, along with details such as the
severity, priority, and description of the issue.
 Test data preparation: Test data is prepared and
loaded into the system for test execution
 Test environment setup: The necessary
hardware, software, and network configurations
are set up for test execution
Contd..
 Test execution: The test cases and scripts
are run, and the results are collected and
analyzed.
 Test result analysis: The results of the test
execution are analyzed to determine the
software’s performance and identify any
defects or issues.
 Defect retesting: Any defects that are
identified during test execution are retested to
ensure that they have been fixed correctly.
 Test Reporting: Test results are documented
and reported to the relevant stakeholders.
6. Test Closure:
 Test closure is the final stage of the Software
Testing Life Cycle (STLC) where all testing-
related activities are completed and
documented.
 The main objective of the test closure stage is
to ensure that all testing-related activities have
been completed and that the software is ready
for release.
The main activities test closure
stage include:
 Test summary report: A report is created that
summarizes the overall testing process,
including the number of test cases executed,
the number of defects found, and the overall
pass/fail rate.
 Defect tracking: All defects that were
identified during testing are tracked and
managed until they are resolved.
 Test environment clean-up: The test
environment is cleaned up, and all test data
and test artifacts are archived.
Contd..
 Test closure report: A report is created that
documents all the testing-related activities that
took place, including the testing objectives, scope,
schedule, and resources used.
 Knowledge transfer: Knowledge about the
software and testing process is shared with the
rest of the team and any stakeholders who may
need to maintain or support the software in the
future.
 Feedback and improvements: Feedback from
the testing process is collected and used to
improve future testing processes
What is a Test Plan?
 A test plan is a detailed document which
describes software testing areas and activities.
 It outlines the test strategy, objectives, test
schedule, required resources (human
resources, software, and hardware), test
estimation and test deliverables.
 The test plan is a base of every software's
testing.
 It is the most crucial activity which ensures
availability of all the lists of planned activities
in an appropriate sequence.
 The test plan is a template for conducting
software testing activities as a defined process
that is fully monitored and controlled by the
testing manager.
 The test plan is prepared by the Test Lead
(60%), Test Manager(20%), and by the test
engineer(20%).
Types of Test Plan
 Master Test Plan
 Phase Test Plan
 Testing Type Specific Test Plans
Contd..
 Master Test Plan
 Master Test Plan is a type of test plan that has
multiple levels of testing. It includes a complete test
strategy.
 Phase Test Plan
 A phase test plan is a type of test plan that addresses
any one phase of the testing strategy. For example, a
list of tools, a list of test cases, etc.
 Specific Test Plans
 Specific test plan designed for major types of testing
like security testing, load testing, performance testing,
etc. In other words, a specific test plan designed for
non-functional testing.
Objectives of the test plan
 Overview of testing activities: The test plan provides an
overview of the testing activities and where to start and stop
the work.
 Provides timeline: The test plan helps to create the timeline
for the testing activities based on the number of hours and
the workers needed.
 Helps to estimate resources: The test plan helps to create
an estimate of the number of resources needed to finish the
work.
 Serves as a blueprint: The test plan serves as a blueprint
for all the testing activities, it has every detail from beginning
to end.
 Helps to identify solutions: A test plan helps the team
members to consider the project’s challenges and identify the
solutions.
 Serves as a rulebook: The test plan serves as a rulebook
for following rules when the project is completed phase by
phase.
Who creates the test plan?
Importance of Test Plan
 Quick guide for the testing process: The test plan serves
as a quick guide for the testing process as it offers a clear
guide for QA engineers to conduct testing activities.
 Helps to avoid out-of-scope functionalities: The test plan
offers detailed aspects such as test scope, test estimation,
strategy, etc.
 Helps to determine the time, cost, and effort: Test serves
as the blueprint to conduct testing activities thus it helps to
deduce an estimate of time, cost, and effort for the testing
activities.
 Provide a schedule for testing activities: A test plan is like
a rule book that needs to be followed, it thus helps to
schedule activities that can be followed by all the team
members.
 Test plan can be reused: The test plan documents
important aspects like test estimation, test scope, and test
strategy which are reviewed by the Management Team and
thus can be reused for other projects.
Components of a test plan
Components of a test plan
 Objectives: It consists of information about
modules, features, test data etc., which indicate
the aim of the application means the application
behavior, goal, etc.
 Scope: It contains information that needs to be
tested with respective of an application. The
Scope can be further divided into two parts:
 In scope: These are the modules that need to be
tested rigorously (in-detail).
 Out scope: These are the modules, which need not
be tested rigorously.
Components of a test plan
 Test methodology:
 It contains information about performing a
different kind of testing like Functional testing,
Integration testing, and System testing, etc. on
the application.
 In this, we will decide what type of testing; we will
perform on the various features based on the
application requirement
Components of a test plan
 Approach
 This attribute is used to describe the flow of
the application while performing testing and for
the future reference.
 We can understand the flow of the application
with the help of below aspects:
 By writing the high-level scenarios
 By writing the flow graph
Components of a test plan
 By writing the high-level scenarios
 For example, suppose we are testing
the Gmail application:
 Login to Gmail- sends an email and check
whether it is in the Sent Items page
 Login to …….
 ……
 …....
Components of a test plan
 By writing the flow
graph
 The flow graph is
written because
writing the high-
level scenarios are
bit time taking
process, as we can
see in the below
image:
Components of a test plan
 Assumption
 It contains information about a problem or issue
which maybe occurred during the testing process
and when we are writing the test plans, the
assured assumptions would be made like
resources and technologies, etc.
 Risk
 These are the challenges which we need to face
to test the application in the current release and if
the assumptions will fail then the risks are
involved.
Components of a test plan
 Mitigation Plan or Contingency Plan
 It is a back-up plan which is prepared to
overcome the risks or issues.
 Role & Responsibility

Components of a test plan
 It defines the complete task which needs to be
performed by the entire testing team.
 When a large project comes, then the Test
Manager is a person who writes the test plan.
 If there are 3-4 small projects, then the test
manager will assign each project to each Test
Lead. And then, the test lead writes the test
plan for the project, which he/she is assigned.
Components of a test plan
 Schedule
 It is used to explain the timing to work, which
needs to be done or this attribute covers when
exactly each testing activity should start and
end? And the exact data is also mentioned for
every testing activity for the particular date.
Components of a test plan
 Defect tracking
 It is generally done with the help of tools because
we cannot track the status of each bug manually.
 And we also comment about how we
communicate the bugs which are identified during
the testing process and send it back to the
development team and how the development
team will reply.
 Here we also mention the priority of the bugs
such as high, medium, and low.
Components of a test plan
 Test Environments
 These are the environments where we will test the
application, and here we have two types of
environments, which are
of software and hardware configuration.
 The software configuration means the details
about different Operating Systems such
as Windows, Linux, UNIX, and Mac and
various Browsers like Google Chrome, Firefox,
Opera, Internet Explorer, and so on.
Components of a test plan
 Entry and Exit criteria
 It is a necessary condition, which needs to be satisfied
before starting and stopping the testing process.
 Entry Criteria
 The entry criteria contain the following conditions:
 White box testing should be finished.
 Understand and analyze the requirement and prepare the
test documents or when the test documents are ready.
 Test data should be ready.
 Build or the application must be prepared
 Modules or features need to be assigned to the different
test engineers.
 The necessary resource must be ready.
Components of a test plan
 Exit Criteria
 The exit criteria contain the following conditions:
 When all the test cases are executed.
 Most of the test cases must be passed.
 Depends on severity of the bugs which means
that there must not be any blocker or major bug,
whereas some minor bugs exist.
Components of a test plan
 Test Automation
 In this, we will decide the following:
 Which feature has to be automated and not to be
automated?
 Which test automation tool we are going to use
on which automation framework?
Components of a test plan
 Effort estimation
 In this, we will plan the effort need to be applied
by every team member.
Components of a test plan
 Test Deliverable
 These are the documents which are the output from
the testing team, which we handed over to the
customer along with the product. It includes the
following:
 Test plan
 Test Cases
 Test Scripts
 RTM(Requirement Traceability Matrix)
 Defect Report
 Test Execution Report
 Graphs and metrics
 Release Notes
Components of a test plan
 Template
 This part contains all the templates for the documents
that will be used in the product, and all the test
engineers will use only these templates in the project
to maintain the consistency of the product. Here, we
have different types of the template which are used
during the entire testing process such as:
 Test case template
 Test case review template
 RTM Template
 Bug Report Template
 Test execution Report
Test Design
 What is Test Design?
 Test design is a process that defines how testing
has to be done. It involves the process of
identifying the testing techniques, test scenarios,
test cases, test data, and expected test results.
 Also, testers need to be specific about the test
cases they create, such as providing specific
inputs, steps, and test data for each test case.
Purpose of Test Design?
 Test design is a process that defines how
testing has to be done.
 It involves the process of identifying the
testing techniques, test scenarios, test
cases, test data, and expected test results.
 Also, testers need to be specific about the
test cases they create, such as providing
specific inputs, steps, and test data for
each test case.
When to Create a Test
Design?
 Test design should be created once the test
conditions are defined, and adequate
information is available to create the test
cases of both high and low levels.
How Is Test Design Done?
 Test design is done using several test
design techniques. The following is a list of
some of the top design techniques,
 Equivalence Class Testing
 State Transition
 Exploratory Testing
 Boundary value analysis
 Pairwise test design
 Error guessing test design
contents
 3.1 Test Planning
 3.2 Test Plan
 3.3 What is a test Plan
 3.4 Who creates a Test Plan
 3.5 When is the Test Plan created
 3.6 Purpose of creating a Test Plan
 3.7 Components of a Test plan.
 3.8 Test design
References
 https://www.javatpoint.com/test-plan
 https://www.geeksforgeeks.org/software-
testing-life-cycle-stlc/?ref=lbp
 https://www.tutorialspoint.com/software_testing
/software_testing_overview.htm
 https://www.geeksforgeeks.org/software-
testing-test-plan/
 https://testsigma.com/blog/test-design/

More Related Content

What's hot

Quality Assurance and Software Testing
Quality Assurance and Software TestingQuality Assurance and Software Testing
Quality Assurance and Software Testingpingkapil
 
Verification and Validation in Manual Testing
Verification and Validation in Manual TestingVerification and Validation in Manual Testing
Verification and Validation in Manual TestingBollapalli Vasundhara
 
Software QA Fundamentals by Prabhath Darshana
Software QA Fundamentals by Prabhath DarshanaSoftware QA Fundamentals by Prabhath Darshana
Software QA Fundamentals by Prabhath DarshanaShamain Peiris
 
Software Quality Assurance
Software Quality Assurance Software Quality Assurance
Software Quality Assurance ShashankBajpai24
 
Software testing course - Manual
Software testing course - ManualSoftware testing course - Manual
Software testing course - ManualPankaj Dubey
 
Chapter 2 - Testing Throughout the Development LifeCycle
Chapter 2 - Testing Throughout the Development LifeCycleChapter 2 - Testing Throughout the Development LifeCycle
Chapter 2 - Testing Throughout the Development LifeCycleNeeraj Kumar Singh
 
Test Management introduction
Test Management introductionTest Management introduction
Test Management introductionOana Feidi
 
01 software test engineering (manual testing)
01 software test engineering (manual testing)01 software test engineering (manual testing)
01 software test engineering (manual testing)Siddireddy Balu
 

What's hot (20)

QACampus PPT (STLC)
QACampus PPT (STLC)QACampus PPT (STLC)
QACampus PPT (STLC)
 
Manual testing ppt
Manual testing pptManual testing ppt
Manual testing ppt
 
Quality Assurance and Software Testing
Quality Assurance and Software TestingQuality Assurance and Software Testing
Quality Assurance and Software Testing
 
STLC
STLCSTLC
STLC
 
Software test life cycle
Software test life cycleSoftware test life cycle
Software test life cycle
 
SDLC vs STLC
SDLC vs STLCSDLC vs STLC
SDLC vs STLC
 
Softwaretesting
SoftwaretestingSoftwaretesting
Softwaretesting
 
Verification and Validation in Manual Testing
Verification and Validation in Manual TestingVerification and Validation in Manual Testing
Verification and Validation in Manual Testing
 
SOFTWARE TESTING
SOFTWARE TESTINGSOFTWARE TESTING
SOFTWARE TESTING
 
Software Testing or Quality Assurance
Software Testing or Quality AssuranceSoftware Testing or Quality Assurance
Software Testing or Quality Assurance
 
Software quality assurance
Software quality assuranceSoftware quality assurance
Software quality assurance
 
Introduction & Manual Testing
Introduction & Manual TestingIntroduction & Manual Testing
Introduction & Manual Testing
 
Software QA Fundamentals by Prabhath Darshana
Software QA Fundamentals by Prabhath DarshanaSoftware QA Fundamentals by Prabhath Darshana
Software QA Fundamentals by Prabhath Darshana
 
Software Quality Assurance
Software Quality Assurance Software Quality Assurance
Software Quality Assurance
 
Test management
Test managementTest management
Test management
 
Software testing course - Manual
Software testing course - ManualSoftware testing course - Manual
Software testing course - Manual
 
Software testing
Software testingSoftware testing
Software testing
 
Chapter 2 - Testing Throughout the Development LifeCycle
Chapter 2 - Testing Throughout the Development LifeCycleChapter 2 - Testing Throughout the Development LifeCycle
Chapter 2 - Testing Throughout the Development LifeCycle
 
Test Management introduction
Test Management introductionTest Management introduction
Test Management introduction
 
01 software test engineering (manual testing)
01 software test engineering (manual testing)01 software test engineering (manual testing)
01 software test engineering (manual testing)
 

Similar to SDET UNIT 3.pptx

Fundamental test process (TESTING IMPLEMENTATION SYSTEM)
Fundamental test process (TESTING IMPLEMENTATION SYSTEM)Fundamental test process (TESTING IMPLEMENTATION SYSTEM)
Fundamental test process (TESTING IMPLEMENTATION SYSTEM)Putri nadya Fazri
 
2 . fundamental test process
2 . fundamental test process2 . fundamental test process
2 . fundamental test processsabrian SIF
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test processIrvan Febry
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test processmuhammad afif
 
Fundamentals of testing
Fundamentals of testingFundamentals of testing
Fundamentals of testingM HiDayat
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test processDinul
 
Fundamental Test Process
Fundamental Test ProcessFundamental Test Process
Fundamental Test ProcessRakhesLeoPutra
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test processYoga Setiawan
 
How to Write a Test Plan .pdf
How to Write a Test Plan .pdfHow to Write a Test Plan .pdf
How to Write a Test Plan .pdfSudhanshiBakre1
 

Similar to SDET UNIT 3.pptx (20)

Stlc ppt
Stlc pptStlc ppt
Stlc ppt
 
Test planning
Test planningTest planning
Test planning
 
CTFL chapter 05
CTFL chapter 05CTFL chapter 05
CTFL chapter 05
 
STLC-ppt-1.pptx
STLC-ppt-1.pptxSTLC-ppt-1.pptx
STLC-ppt-1.pptx
 
Fundamental test process (TESTING IMPLEMENTATION SYSTEM)
Fundamental test process (TESTING IMPLEMENTATION SYSTEM)Fundamental test process (TESTING IMPLEMENTATION SYSTEM)
Fundamental test process (TESTING IMPLEMENTATION SYSTEM)
 
2 . fundamental test process
2 . fundamental test process2 . fundamental test process
2 . fundamental test process
 
stlc
stlcstlc
stlc
 
Fundamental Test Process
Fundamental Test ProcessFundamental Test Process
Fundamental Test Process
 
SOFTWARE TESTING
SOFTWARE TESTINGSOFTWARE TESTING
SOFTWARE TESTING
 
stlc
stlcstlc
stlc
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test process
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test process
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test process
 
Stlc&Vmodel Ppt
Stlc&Vmodel PptStlc&Vmodel Ppt
Stlc&Vmodel Ppt
 
Fundamentals of testing
Fundamentals of testingFundamentals of testing
Fundamentals of testing
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test process
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test process
 
Fundamental Test Process
Fundamental Test ProcessFundamental Test Process
Fundamental Test Process
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test process
 
How to Write a Test Plan .pdf
How to Write a Test Plan .pdfHow to Write a Test Plan .pdf
How to Write a Test Plan .pdf
 

More from PallawiBulakh1

Research Methodology UNIT 4.pptx
Research Methodology UNIT 4.pptxResearch Methodology UNIT 4.pptx
Research Methodology UNIT 4.pptxPallawiBulakh1
 
Research Methodology UNIT 3.pptx
Research Methodology UNIT 3.pptxResearch Methodology UNIT 3.pptx
Research Methodology UNIT 3.pptxPallawiBulakh1
 
Research Methodology UNIT 2.pptx
Research Methodology UNIT 2.pptxResearch Methodology UNIT 2.pptx
Research Methodology UNIT 2.pptxPallawiBulakh1
 
Research Methodology UNIT 1.pptx
Research Methodology UNIT 1.pptxResearch Methodology UNIT 1.pptx
Research Methodology UNIT 1.pptxPallawiBulakh1
 
Introduction to web technology
Introduction to web technologyIntroduction to web technology
Introduction to web technologyPallawiBulakh1
 
How to write and publish good quality research paper
How to write and publish good quality research paperHow to write and publish good quality research paper
How to write and publish good quality research paperPallawiBulakh1
 

More from PallawiBulakh1 (12)

ch13.ppt
ch13.pptch13.ppt
ch13.ppt
 
RM UNIT 6.pptx
RM UNIT 6.pptxRM UNIT 6.pptx
RM UNIT 6.pptx
 
RM UNIT 5.pptx
RM UNIT 5.pptxRM UNIT 5.pptx
RM UNIT 5.pptx
 
Research Methodology UNIT 4.pptx
Research Methodology UNIT 4.pptxResearch Methodology UNIT 4.pptx
Research Methodology UNIT 4.pptx
 
Research Methodology UNIT 3.pptx
Research Methodology UNIT 3.pptxResearch Methodology UNIT 3.pptx
Research Methodology UNIT 3.pptx
 
Research Methodology UNIT 2.pptx
Research Methodology UNIT 2.pptxResearch Methodology UNIT 2.pptx
Research Methodology UNIT 2.pptx
 
Research Methodology UNIT 1.pptx
Research Methodology UNIT 1.pptxResearch Methodology UNIT 1.pptx
Research Methodology UNIT 1.pptx
 
Msword module 3
Msword  module 3Msword  module 3
Msword module 3
 
Ms word module 2
Ms word  module 2Ms word  module 2
Ms word module 2
 
Introduction to web technology
Introduction to web technologyIntroduction to web technology
Introduction to web technology
 
Ms word module 1
Ms word module 1Ms word module 1
Ms word module 1
 
How to write and publish good quality research paper
How to write and publish good quality research paperHow to write and publish good quality research paper
How to write and publish good quality research paper
 

Recently uploaded

DIFFERENT BASKETRY IN THE PHILIPPINES PPT.pptx
DIFFERENT BASKETRY IN THE PHILIPPINES PPT.pptxDIFFERENT BASKETRY IN THE PHILIPPINES PPT.pptx
DIFFERENT BASKETRY IN THE PHILIPPINES PPT.pptxMichelleTuguinay1
 
Q-Factor HISPOL Quiz-6th April 2024, Quiz Club NITW
Q-Factor HISPOL Quiz-6th April 2024, Quiz Club NITWQ-Factor HISPOL Quiz-6th April 2024, Quiz Club NITW
Q-Factor HISPOL Quiz-6th April 2024, Quiz Club NITWQuiz Club NITW
 
ROLES IN A STAGE PRODUCTION in arts.pptx
ROLES IN A STAGE PRODUCTION in arts.pptxROLES IN A STAGE PRODUCTION in arts.pptx
ROLES IN A STAGE PRODUCTION in arts.pptxVanesaIglesias10
 
ANG SEKTOR NG agrikultura.pptx QUARTER 4
ANG SEKTOR NG agrikultura.pptx QUARTER 4ANG SEKTOR NG agrikultura.pptx QUARTER 4
ANG SEKTOR NG agrikultura.pptx QUARTER 4MiaBumagat1
 
week 1 cookery 8 fourth - quarter .pptx
week 1 cookery 8  fourth  -  quarter .pptxweek 1 cookery 8  fourth  -  quarter .pptx
week 1 cookery 8 fourth - quarter .pptxJonalynLegaspi2
 
Influencing policy (training slides from Fast Track Impact)
Influencing policy (training slides from Fast Track Impact)Influencing policy (training slides from Fast Track Impact)
Influencing policy (training slides from Fast Track Impact)Mark Reed
 
INTRODUCTION TO CATHOLIC CHRISTOLOGY.pptx
INTRODUCTION TO CATHOLIC CHRISTOLOGY.pptxINTRODUCTION TO CATHOLIC CHRISTOLOGY.pptx
INTRODUCTION TO CATHOLIC CHRISTOLOGY.pptxHumphrey A Beña
 
THEORIES OF ORGANIZATION-PUBLIC ADMINISTRATION
THEORIES OF ORGANIZATION-PUBLIC ADMINISTRATIONTHEORIES OF ORGANIZATION-PUBLIC ADMINISTRATION
THEORIES OF ORGANIZATION-PUBLIC ADMINISTRATIONHumphrey A Beña
 
Oppenheimer Film Discussion for Philosophy and Film
Oppenheimer Film Discussion for Philosophy and FilmOppenheimer Film Discussion for Philosophy and Film
Oppenheimer Film Discussion for Philosophy and FilmStan Meyer
 
BIOCHEMISTRY-CARBOHYDRATE METABOLISM CHAPTER 2.pptx
BIOCHEMISTRY-CARBOHYDRATE METABOLISM CHAPTER 2.pptxBIOCHEMISTRY-CARBOHYDRATE METABOLISM CHAPTER 2.pptx
BIOCHEMISTRY-CARBOHYDRATE METABOLISM CHAPTER 2.pptxSayali Powar
 
Reading and Writing Skills 11 quarter 4 melc 1
Reading and Writing Skills 11 quarter 4 melc 1Reading and Writing Skills 11 quarter 4 melc 1
Reading and Writing Skills 11 quarter 4 melc 1GloryAnnCastre1
 
4.18.24 Movement Legacies, Reflection, and Review.pptx
4.18.24 Movement Legacies, Reflection, and Review.pptx4.18.24 Movement Legacies, Reflection, and Review.pptx
4.18.24 Movement Legacies, Reflection, and Review.pptxmary850239
 
Transaction Management in Database Management System
Transaction Management in Database Management SystemTransaction Management in Database Management System
Transaction Management in Database Management SystemChristalin Nelson
 
ICS2208 Lecture6 Notes for SL spaces.pdf
ICS2208 Lecture6 Notes for SL spaces.pdfICS2208 Lecture6 Notes for SL spaces.pdf
ICS2208 Lecture6 Notes for SL spaces.pdfVanessa Camilleri
 
Choosing the Right CBSE School A Comprehensive Guide for Parents
Choosing the Right CBSE School A Comprehensive Guide for ParentsChoosing the Right CBSE School A Comprehensive Guide for Parents
Choosing the Right CBSE School A Comprehensive Guide for Parentsnavabharathschool99
 
Mental Health Awareness - a toolkit for supporting young minds
Mental Health Awareness - a toolkit for supporting young mindsMental Health Awareness - a toolkit for supporting young minds
Mental Health Awareness - a toolkit for supporting young mindsPooky Knightsmith
 
Grade Three -ELLNA-REVIEWER-ENGLISH.pptx
Grade Three -ELLNA-REVIEWER-ENGLISH.pptxGrade Three -ELLNA-REVIEWER-ENGLISH.pptx
Grade Three -ELLNA-REVIEWER-ENGLISH.pptxkarenfajardo43
 
Congestive Cardiac Failure..presentation
Congestive Cardiac Failure..presentationCongestive Cardiac Failure..presentation
Congestive Cardiac Failure..presentationdeepaannamalai16
 

Recently uploaded (20)

DIFFERENT BASKETRY IN THE PHILIPPINES PPT.pptx
DIFFERENT BASKETRY IN THE PHILIPPINES PPT.pptxDIFFERENT BASKETRY IN THE PHILIPPINES PPT.pptx
DIFFERENT BASKETRY IN THE PHILIPPINES PPT.pptx
 
Mattingly "AI & Prompt Design: Large Language Models"
Mattingly "AI & Prompt Design: Large Language Models"Mattingly "AI & Prompt Design: Large Language Models"
Mattingly "AI & Prompt Design: Large Language Models"
 
Q-Factor HISPOL Quiz-6th April 2024, Quiz Club NITW
Q-Factor HISPOL Quiz-6th April 2024, Quiz Club NITWQ-Factor HISPOL Quiz-6th April 2024, Quiz Club NITW
Q-Factor HISPOL Quiz-6th April 2024, Quiz Club NITW
 
ROLES IN A STAGE PRODUCTION in arts.pptx
ROLES IN A STAGE PRODUCTION in arts.pptxROLES IN A STAGE PRODUCTION in arts.pptx
ROLES IN A STAGE PRODUCTION in arts.pptx
 
ANG SEKTOR NG agrikultura.pptx QUARTER 4
ANG SEKTOR NG agrikultura.pptx QUARTER 4ANG SEKTOR NG agrikultura.pptx QUARTER 4
ANG SEKTOR NG agrikultura.pptx QUARTER 4
 
week 1 cookery 8 fourth - quarter .pptx
week 1 cookery 8  fourth  -  quarter .pptxweek 1 cookery 8  fourth  -  quarter .pptx
week 1 cookery 8 fourth - quarter .pptx
 
Influencing policy (training slides from Fast Track Impact)
Influencing policy (training slides from Fast Track Impact)Influencing policy (training slides from Fast Track Impact)
Influencing policy (training slides from Fast Track Impact)
 
INTRODUCTION TO CATHOLIC CHRISTOLOGY.pptx
INTRODUCTION TO CATHOLIC CHRISTOLOGY.pptxINTRODUCTION TO CATHOLIC CHRISTOLOGY.pptx
INTRODUCTION TO CATHOLIC CHRISTOLOGY.pptx
 
THEORIES OF ORGANIZATION-PUBLIC ADMINISTRATION
THEORIES OF ORGANIZATION-PUBLIC ADMINISTRATIONTHEORIES OF ORGANIZATION-PUBLIC ADMINISTRATION
THEORIES OF ORGANIZATION-PUBLIC ADMINISTRATION
 
Oppenheimer Film Discussion for Philosophy and Film
Oppenheimer Film Discussion for Philosophy and FilmOppenheimer Film Discussion for Philosophy and Film
Oppenheimer Film Discussion for Philosophy and Film
 
BIOCHEMISTRY-CARBOHYDRATE METABOLISM CHAPTER 2.pptx
BIOCHEMISTRY-CARBOHYDRATE METABOLISM CHAPTER 2.pptxBIOCHEMISTRY-CARBOHYDRATE METABOLISM CHAPTER 2.pptx
BIOCHEMISTRY-CARBOHYDRATE METABOLISM CHAPTER 2.pptx
 
Reading and Writing Skills 11 quarter 4 melc 1
Reading and Writing Skills 11 quarter 4 melc 1Reading and Writing Skills 11 quarter 4 melc 1
Reading and Writing Skills 11 quarter 4 melc 1
 
4.18.24 Movement Legacies, Reflection, and Review.pptx
4.18.24 Movement Legacies, Reflection, and Review.pptx4.18.24 Movement Legacies, Reflection, and Review.pptx
4.18.24 Movement Legacies, Reflection, and Review.pptx
 
Transaction Management in Database Management System
Transaction Management in Database Management SystemTransaction Management in Database Management System
Transaction Management in Database Management System
 
ICS2208 Lecture6 Notes for SL spaces.pdf
ICS2208 Lecture6 Notes for SL spaces.pdfICS2208 Lecture6 Notes for SL spaces.pdf
ICS2208 Lecture6 Notes for SL spaces.pdf
 
Paradigm shift in nursing research by RS MEHTA
Paradigm shift in nursing research by RS MEHTAParadigm shift in nursing research by RS MEHTA
Paradigm shift in nursing research by RS MEHTA
 
Choosing the Right CBSE School A Comprehensive Guide for Parents
Choosing the Right CBSE School A Comprehensive Guide for ParentsChoosing the Right CBSE School A Comprehensive Guide for Parents
Choosing the Right CBSE School A Comprehensive Guide for Parents
 
Mental Health Awareness - a toolkit for supporting young minds
Mental Health Awareness - a toolkit for supporting young mindsMental Health Awareness - a toolkit for supporting young minds
Mental Health Awareness - a toolkit for supporting young minds
 
Grade Three -ELLNA-REVIEWER-ENGLISH.pptx
Grade Three -ELLNA-REVIEWER-ENGLISH.pptxGrade Three -ELLNA-REVIEWER-ENGLISH.pptx
Grade Three -ELLNA-REVIEWER-ENGLISH.pptx
 
Congestive Cardiac Failure..presentation
Congestive Cardiac Failure..presentationCongestive Cardiac Failure..presentation
Congestive Cardiac Failure..presentation
 

SDET UNIT 3.pptx

  • 1. UNIT 3 SOFTWARE TESTING LIFE CYCLE Dr. Pallawi Bulakh
  • 2. contents  3.1 Test Planning  3.2 Test Plan  3.3 What is a test Plan  3.4 Who creates a Test Plan  3.5 When is the Test Plan created  3.6 Purpose of creating a Test Plan  3.7 Components of a Test plan.  3.8 Test design  3.9 Test implementation and Execution  3.10 Defect Reporting and tracking  3.11 Defect life cycle  3.12 Test closures  3.13 Test metrics
  • 3. STLC  The Software Testing Life Cycle (STLC) is a systematic approach to testing a software application to ensure that it meets the requirements and is free of defects. It is a process that follows a series of steps or phases, and each phase has specific objectives and deliverables.  The STLC is used to ensure that the software is of high quality, reliable, and meets the needs of the end-users.
  • 4. STLC  The main goal of the STLC is to identify and document any defects or issues in the software application as early as possible in the development process.  This allows for issues to be addressed and resolved before the software is released to the public.
  • 5. Characteristics of STLC  STLC is a fundamental part of the Software Development Life Cycle (SDLC) but STLC consists of only the testing phases.  STLC starts as soon as requirements are defined or software requirement document is shared by stakeholders.  STLC yields a step-by-step process to ensure quality software.
  • 7. 1. Requirement Analysis  Requirement Analysis is the first step of the Software Testing Life Cycle (STLC).  In this phase quality assurance team understands the requirements like what is to be tested.  If anything is missing or not understandable then the quality assurance team meets with the stakeholders to better understand the detailed knowledge of requirements.
  • 8. The activities during the Requirement Analysis stage :  Reviewing the software requirements document (SRD) and other related documents  Interviewing stakeholders to gather additional information  Identifying any ambiguities or inconsistencies in the requirements  Identifying any missing or incomplete requirements  Identifying any potential risks or issues that may impact the testing process
  • 9. 2. Test Planning:  Test Planning is the most efficient phase of the software testing life cycle where all testing plans are defined.  In this phase manager of the testing, team calculates the estimated effort and cost for the testing work.  This phase gets started once the requirement- gathering phase is completed.
  • 10. The activities during the Test Planning stage  Identifying the testing objectives and scope  Developing a test strategy: selecting the testing methods and techniques that will be used  Identifying the testing environment and resources needed  Identifying the test cases that will be executed and the test data that will be used  Estimating the time and cost required for testing  Identifying the test deliverables and milestones  Assigning roles and responsibilities to the testing team  Reviewing and approving the test plan
  • 11. Test Case Development:  The test case development phase gets started once the test planning phase is completed.  In this phase testing team notes down the detailed test cases.  The testing team also prepares the required test data for the testing.  When the test cases are prepared then they are reviewed by the quality assurance team.
  • 12. The activities during the Test Case Development stage :  Identifying the test cases that will be developed  Writing test cases that are clear, concise, and easy to understand  Creating test data and test scenarios that will be used in the test cases  Identifying the expected results for each test case  Reviewing and validating the test cases  Updating the requirement traceability matrix (RTM) to map requirements to test cases.
  • 13. 4.Test Environment Setup  Test environment setup is a vital part of the STLC. Basically, the test environment decides the conditions on which software is tested.  This is independent activity and can be started along with test case development.  In this process, the testing team is not involved. either the developer or the customer creates the testing environment.
  • 14. 5. Test Execution:  After the test case development and test environment setup test execution phase gets started.  In this phase testing team starts executing test cases based on prepared test cases in the earlier step.
  • 15. The activities during the test execution stage  Test execution: The test cases and scripts created in the test design stage are run against the software application to identify any defects or issues.  Defect logging: Any defects or issues that are found during test execution are logged in a defect tracking system, along with details such as the severity, priority, and description of the issue.  Test data preparation: Test data is prepared and loaded into the system for test execution  Test environment setup: The necessary hardware, software, and network configurations are set up for test execution
  • 16. Contd..  Test execution: The test cases and scripts are run, and the results are collected and analyzed.  Test result analysis: The results of the test execution are analyzed to determine the software’s performance and identify any defects or issues.  Defect retesting: Any defects that are identified during test execution are retested to ensure that they have been fixed correctly.  Test Reporting: Test results are documented and reported to the relevant stakeholders.
  • 17. 6. Test Closure:  Test closure is the final stage of the Software Testing Life Cycle (STLC) where all testing- related activities are completed and documented.  The main objective of the test closure stage is to ensure that all testing-related activities have been completed and that the software is ready for release.
  • 18. The main activities test closure stage include:  Test summary report: A report is created that summarizes the overall testing process, including the number of test cases executed, the number of defects found, and the overall pass/fail rate.  Defect tracking: All defects that were identified during testing are tracked and managed until they are resolved.  Test environment clean-up: The test environment is cleaned up, and all test data and test artifacts are archived.
  • 19. Contd..  Test closure report: A report is created that documents all the testing-related activities that took place, including the testing objectives, scope, schedule, and resources used.  Knowledge transfer: Knowledge about the software and testing process is shared with the rest of the team and any stakeholders who may need to maintain or support the software in the future.  Feedback and improvements: Feedback from the testing process is collected and used to improve future testing processes
  • 20. What is a Test Plan?  A test plan is a detailed document which describes software testing areas and activities.  It outlines the test strategy, objectives, test schedule, required resources (human resources, software, and hardware), test estimation and test deliverables.  The test plan is a base of every software's testing.
  • 21.  It is the most crucial activity which ensures availability of all the lists of planned activities in an appropriate sequence.  The test plan is a template for conducting software testing activities as a defined process that is fully monitored and controlled by the testing manager.  The test plan is prepared by the Test Lead (60%), Test Manager(20%), and by the test engineer(20%).
  • 22. Types of Test Plan  Master Test Plan  Phase Test Plan  Testing Type Specific Test Plans
  • 23. Contd..  Master Test Plan  Master Test Plan is a type of test plan that has multiple levels of testing. It includes a complete test strategy.  Phase Test Plan  A phase test plan is a type of test plan that addresses any one phase of the testing strategy. For example, a list of tools, a list of test cases, etc.  Specific Test Plans  Specific test plan designed for major types of testing like security testing, load testing, performance testing, etc. In other words, a specific test plan designed for non-functional testing.
  • 24. Objectives of the test plan  Overview of testing activities: The test plan provides an overview of the testing activities and where to start and stop the work.  Provides timeline: The test plan helps to create the timeline for the testing activities based on the number of hours and the workers needed.  Helps to estimate resources: The test plan helps to create an estimate of the number of resources needed to finish the work.  Serves as a blueprint: The test plan serves as a blueprint for all the testing activities, it has every detail from beginning to end.  Helps to identify solutions: A test plan helps the team members to consider the project’s challenges and identify the solutions.  Serves as a rulebook: The test plan serves as a rulebook for following rules when the project is completed phase by phase.
  • 25. Who creates the test plan?
  • 26. Importance of Test Plan  Quick guide for the testing process: The test plan serves as a quick guide for the testing process as it offers a clear guide for QA engineers to conduct testing activities.  Helps to avoid out-of-scope functionalities: The test plan offers detailed aspects such as test scope, test estimation, strategy, etc.  Helps to determine the time, cost, and effort: Test serves as the blueprint to conduct testing activities thus it helps to deduce an estimate of time, cost, and effort for the testing activities.  Provide a schedule for testing activities: A test plan is like a rule book that needs to be followed, it thus helps to schedule activities that can be followed by all the team members.  Test plan can be reused: The test plan documents important aspects like test estimation, test scope, and test strategy which are reviewed by the Management Team and thus can be reused for other projects.
  • 27. Components of a test plan
  • 28. Components of a test plan  Objectives: It consists of information about modules, features, test data etc., which indicate the aim of the application means the application behavior, goal, etc.  Scope: It contains information that needs to be tested with respective of an application. The Scope can be further divided into two parts:  In scope: These are the modules that need to be tested rigorously (in-detail).  Out scope: These are the modules, which need not be tested rigorously.
  • 29. Components of a test plan  Test methodology:  It contains information about performing a different kind of testing like Functional testing, Integration testing, and System testing, etc. on the application.  In this, we will decide what type of testing; we will perform on the various features based on the application requirement
  • 30. Components of a test plan  Approach  This attribute is used to describe the flow of the application while performing testing and for the future reference.  We can understand the flow of the application with the help of below aspects:  By writing the high-level scenarios  By writing the flow graph
  • 31. Components of a test plan  By writing the high-level scenarios  For example, suppose we are testing the Gmail application:  Login to Gmail- sends an email and check whether it is in the Sent Items page  Login to …….  ……  …....
  • 32. Components of a test plan  By writing the flow graph  The flow graph is written because writing the high- level scenarios are bit time taking process, as we can see in the below image:
  • 33. Components of a test plan  Assumption  It contains information about a problem or issue which maybe occurred during the testing process and when we are writing the test plans, the assured assumptions would be made like resources and technologies, etc.  Risk  These are the challenges which we need to face to test the application in the current release and if the assumptions will fail then the risks are involved.
  • 34. Components of a test plan  Mitigation Plan or Contingency Plan  It is a back-up plan which is prepared to overcome the risks or issues.  Role & Responsibility 
  • 35. Components of a test plan  It defines the complete task which needs to be performed by the entire testing team.  When a large project comes, then the Test Manager is a person who writes the test plan.  If there are 3-4 small projects, then the test manager will assign each project to each Test Lead. And then, the test lead writes the test plan for the project, which he/she is assigned.
  • 36. Components of a test plan  Schedule  It is used to explain the timing to work, which needs to be done or this attribute covers when exactly each testing activity should start and end? And the exact data is also mentioned for every testing activity for the particular date.
  • 37. Components of a test plan  Defect tracking  It is generally done with the help of tools because we cannot track the status of each bug manually.  And we also comment about how we communicate the bugs which are identified during the testing process and send it back to the development team and how the development team will reply.  Here we also mention the priority of the bugs such as high, medium, and low.
  • 38. Components of a test plan  Test Environments  These are the environments where we will test the application, and here we have two types of environments, which are of software and hardware configuration.  The software configuration means the details about different Operating Systems such as Windows, Linux, UNIX, and Mac and various Browsers like Google Chrome, Firefox, Opera, Internet Explorer, and so on.
  • 39. Components of a test plan  Entry and Exit criteria  It is a necessary condition, which needs to be satisfied before starting and stopping the testing process.  Entry Criteria  The entry criteria contain the following conditions:  White box testing should be finished.  Understand and analyze the requirement and prepare the test documents or when the test documents are ready.  Test data should be ready.  Build or the application must be prepared  Modules or features need to be assigned to the different test engineers.  The necessary resource must be ready.
  • 40. Components of a test plan  Exit Criteria  The exit criteria contain the following conditions:  When all the test cases are executed.  Most of the test cases must be passed.  Depends on severity of the bugs which means that there must not be any blocker or major bug, whereas some minor bugs exist.
  • 41. Components of a test plan  Test Automation  In this, we will decide the following:  Which feature has to be automated and not to be automated?  Which test automation tool we are going to use on which automation framework?
  • 42. Components of a test plan  Effort estimation  In this, we will plan the effort need to be applied by every team member.
  • 43. Components of a test plan  Test Deliverable  These are the documents which are the output from the testing team, which we handed over to the customer along with the product. It includes the following:  Test plan  Test Cases  Test Scripts  RTM(Requirement Traceability Matrix)  Defect Report  Test Execution Report  Graphs and metrics  Release Notes
  • 44. Components of a test plan  Template  This part contains all the templates for the documents that will be used in the product, and all the test engineers will use only these templates in the project to maintain the consistency of the product. Here, we have different types of the template which are used during the entire testing process such as:  Test case template  Test case review template  RTM Template  Bug Report Template  Test execution Report
  • 45. Test Design  What is Test Design?  Test design is a process that defines how testing has to be done. It involves the process of identifying the testing techniques, test scenarios, test cases, test data, and expected test results.  Also, testers need to be specific about the test cases they create, such as providing specific inputs, steps, and test data for each test case.
  • 46. Purpose of Test Design?  Test design is a process that defines how testing has to be done.  It involves the process of identifying the testing techniques, test scenarios, test cases, test data, and expected test results.  Also, testers need to be specific about the test cases they create, such as providing specific inputs, steps, and test data for each test case.
  • 47. When to Create a Test Design?  Test design should be created once the test conditions are defined, and adequate information is available to create the test cases of both high and low levels.
  • 48. How Is Test Design Done?  Test design is done using several test design techniques. The following is a list of some of the top design techniques,  Equivalence Class Testing  State Transition  Exploratory Testing  Boundary value analysis  Pairwise test design  Error guessing test design
  • 49. contents  3.1 Test Planning  3.2 Test Plan  3.3 What is a test Plan  3.4 Who creates a Test Plan  3.5 When is the Test Plan created  3.6 Purpose of creating a Test Plan  3.7 Components of a Test plan.  3.8 Test design
  • 50. References  https://www.javatpoint.com/test-plan  https://www.geeksforgeeks.org/software- testing-life-cycle-stlc/?ref=lbp  https://www.tutorialspoint.com/software_testing /software_testing_overview.htm  https://www.geeksforgeeks.org/software- testing-test-plan/  https://testsigma.com/blog/test-design/