Introduction of Software Testing

Software testing life cycle, Types &

flavors of testing

Software Testing Slide 1

Software Testing Life Cycle -
STLC

Software Testing Slide 2

 STLC - Definition
The course of software being tested in a well-planned way is known as
Software test life cycle.

Contract Requirement Test Test

Signing Analysis Planning Development

Test Cycle Retest Test Test Env.

Closure Defects Execution Setup

Each stage has a well defined Entry and Exit Criteria, Activities &
Deliverables associated with it.

Software Testing Slide 3

 STLC Stages
STLC Stage Entry Criteria Activity Exit Criteria Deliverables

- Requirements - Identify types of tests to be

Document performed.
available (both - Gather details about testing priorities
functional and non and focus.
- RTM
functional) - Prepare Requirement Traceability - Signed off RTM
Requirement - Automation
- Acceptance Matrix (RTM). - Test automation feasibility
Analysis feasibility report (if
criteria defined. - Identify test environment details report signed off by the client
applicable)
- Application where testing is supposed to be
architectural carried out.
Document - Automation feasibility analysis (if
available. required).

- Requirements
- Preparation of test plan/strategy
Documents
document for various types of testing - Test plan
- Requirement - Approved test plan/strategy
- Test tool selection /strategy
Traceability matrix. document.
Test Planning - Test effort estimation document.
- Test automation - Effort estimation document
- Resource planning and determining - Effort estimation
feasibility signed off.
roles and responsibilities. document.
document.
- Training requirement

Software Testing Slide 4

 STLC Stages

STLC Stage Entry Criteria Activity Exit Criteria Deliverables

- Requirements - Create test cases, automation scripts
- Reviewed and signed test
Documents (where applicable)
Test case Cases/scripts - Test cases/scripts
- RTM and test plan - Review and baseline test cases and
development - Reviewed and signed test - Test data
- Automation scripts
data
analysis report - Create test data

- Understand the required architecture,

environment set-up
- System Design - Environment
- Prepare hardware and software - Environment setup is
and architecture ready with test
requirement list working as per the plan and
Test Environment documents are data set up
- Prepare environment setup checklist checklist
setup available - Smoke Test
- Setup test Environment and test data - Test data setup is complete
- Environment set- Results.
- Perform smoke test on the build - Smoke test is successful
up plan is available
- Accept/reject the build depending on
smoke test result

Software Testing Slide 5

 STLC Stages
STLC Stage Entry Criteria Activity Exit Criteria Deliverables
- Baselined RTM,
Test Plan , Test
- Execute tests as per plan
case/scripts are
- Document test results, and log - Completed RTM
available
defects for failed cases with execution
- Test environment - All tests planned are
- Update test plans/test cases, if status
is ready executed
Test Execution necessary - Test cases
- Test data set up - Defects logged and tracked
- Map defects to test cases in RTM updated with
is done to closure
- Retest the defect fixes results
- Unit/Integration
- Regression testing of application - Defect reports
test report for the
- Track the defects to closure
build to be tested
is available
- Evaluate cycle completion criteria
based on - Time, Test coverage , Cost ,
Softw are - Quality , Critical Business
Objectives
- Testing has been - Prepare test metrics based on the
completed above parameters.
- Test Closure
- Test results are - Document the learning out of the Test Closure report signed
Test Cycle closure report
available project off by client
- Test metrics
- Defect logs are - Prepare Test closure report
available - Qualitative and quantitative reporting
of quality of the w ork product to the
customer.
- Test result analysis to find out the
defect distribution by type and severity

Software Testing Slide 6

 DetailedTest Life Cycle
– V&V (or W) Process Model

Business Acceptance Tests

requirements, Master Test Strategy Release &
Solution Certification
Architecture

Performance
Project Planning Test Planning Integrated Testing,
Solution Business Cycle
testing

HLD/LLD for each Strategy for

application individual Application Incremental
involved applications, Test Integration Integration Testing
Interface design case design

Solution Mapping/ System Testing

Development/ (Application level
Customization Testing)

Software Testing Slide 7

Software Testing - Types

Software Testing Slide 8

 Types of Testing
l Testing type based on the l Testing targets based on
method used life cycle phase
• White-box • Unit testing
• Black-box • Integration testing
l Testing levels based on • System testing
requirement type l Testing needs based on
• Functional needs
• Non-functional l Regression testing
l Acceptance testing
l Alpha & Beta testing

Software Testing Slide 9

Testing Types – Based on Method Used

l Testing type based on the method used

• White-box – Focused on Code
• Black-box – Focused on Requirements
l Objective being to achieve higher test
coverage (both requirements and code
coverage)

Software Testing Slide 10

Testing Types – Based on Requirement Type

l Testing levels based on requirement type

• Functional
• Non-functional
l Functional testing could either be Black-box or
White-box testing
l Non-functional testing could be any of the
following
• Load/ Stress Testing
• Usability/ Compatibility Testing
• Localization Testing etc.

Software Testing Slide 11

Testing Types - Based on life cycle phase

l Testing targets based on life cycle phase

• Unit testing – using White-box testing
• Integration testing – using White/Black-box testing
• System testing – using Black-box testing
• Focus changes from module-level to sub-system level to
entire system

Software Testing Slide 12

 Testing Types - Based on needs
l Testing needs based on needs
l Regression testing
l Acceptance testing
l Alpha & Beta testing
l Performed with a specific need or focus
l Regression testing – to ensure changes have not
impacted existing functionality or behavior
l Acceptance testing – performed by customer
before accepting the software into production
l Alpha – with limited user base at development site
l Beta – with larger end user base at customer site
Software Testing Slide 13