Software Testing Strategies

Introduction
• A strategy for software testing integrates the design of software
test cases into a well-planned series of steps that result in
successful development of the software.

• The strategy provides a road map that describes the steps to be

taken, when, and how much effort, time, and resources will be
required.

• The strategy provides guidance for the practitioner and a set of

milestones for the manager.
• The strategy incorporates
i) test planning
ii) test case design
iii) test execution,
iv) test result collection and evaluation 2
 Testing ??
• Testing is a set of activities that can be
planned in advance and conducted
systematically.

3
 Example of testcase
Test Case ID Test Scenario Test Steps Test Data Expected Results Actual Results Pass/Fail

TU01 Check Customer 1.Go to site http:// Userid = xyz User should Login As Expected Pass
Login with valid demo.xyz.com Password = into an application
Data 2.Enter UserId pass99
3.Enter Password
4.Click Submit

TU02 Check Customer 1.Go to site http:// Userid = xyz User should not As Expected Pass
Login with invalid demo.xyz.com Password = Login into an
Data 2.Enter UserId glass99 application
3.Enter Password
4.Click Submit

4
A Strategic Approach to Testing
 General Characteristics of Strategic Testing
1. To perform effective testing, a software team should
conduct effective formal technical reviews

2. Testing begins at the component level and work outward

toward the integration of the entire computer-based system

3. Different testing techniques are appropriate at different

points in time

4. Testing is conducted by the developer of the software and

(for large projects) by an independent test group

5. Testing and debugging are different activities, but debugging

must be accommodated in any testing strategy
6
Verification and Validation

7
 Verification and Validation
• Software testing is part of a broader group of activities called
verification and validation that are involved in software quality
assurance
• Verification (Are the algorithms coded correctly?)
– The set of activities that ensure that software correctly
implements a specific function or algorithm
– Are we building the product right?

• Validation (Does it meet user requirements?)

– The set of activities that ensure that the software that has
been built is traceable to customer requirements
– Are we building the right product ?

8
 Validation
Verification
Verification refers to the set of activities that Validation refers to the set of activities that ensure
Definition ensure software correctly implements the that the software that has been built is traceable to
specific function customer requirements.
It includes checking documents, designs, codes,
Focus It includes testing and validating the actual product.
and programs.
Type of Testing Verification is the static testing. Validation is dynamic testing.
Execution It does not include the execution of the code. It includes the execution of the code.

Methods used in verification are reviews, Methods used in validation are Black Box Testing,
Methods Used
walkthroughs, inspections and desk-checking. White Box Testing and non-functional testing.

It checks whether the software meets the

It checks whether the software conforms to
Purpose requirements and expectations of a customer or
specifications or not.
not.
It can find the bugs in the early stage of the It can only find the bugs that could not be found by
Bug
development. the verification process.
Human or It consists of checking of documents/files and is It consists of execution of program and is
Computer performed by human. performed by computer.
Verification is also termed as white box testing
Another Validation can be termed as black box testing or
or static testing as work product goes through
Terminology dynamic testing as work product is executed.
reviews.

9
 Real-World Example of Verification vs
Validation
• Verification Example: Imagine a team is developing a new
mobile banking app.
• During the verification phase, they review the requirements
and design documents.
• They check if all the specified features like fund transfer,
account balance check, and transaction history are included
and correctly detailed in the design.
• They also perform peer reviews and inspections to ensure the
design aligns with the requirements.
• This step ensures that the app is being built according to the
initial plan and specifications without actually running the
app.

10
• Validation Example: In the validation phase, the team starts
testing the mobile banking app on actual devices.
• They check if users can log in, transfer money, and view their
transaction history as intended.
• Testers perform usability tests to ensure the app is user-
friendly and functional tests to ensure all features work
correctly.
• They might also involve real users to provide feedback on the
app’s performance.
• This phase ensures that the app works as expected and meets
user needs in real-world scenarios.

11
A Strategy for Testing Conventional
Software

System Testing

r s to
pe
Validation Testing

de w
co
o a ro
Br Nar
Integration Testing
Unit Testing

Code
Design
re to
nc t
co strac
te

Requirements
Ab

System Engineering

12
• Initially, system engineering defines the role of software
and leads to software requirements analysis, where the
information domain, function, behavior, performance,
constraints, and validation criteria for software are
established.

• Moving inward along the spiral, you come to design and

finally to coding.

• To develop computer software, you spiral inward

(counterclockwise) along streamlines that decrease the
level of abstraction on each turn.

13
• Unit testing begins at the vortex of the spiral and concentrates on each unit
(e.g., component, class, or WebApp content object) of the software as
implemented in source code.

• Testing progresses by moving outward along the spiral to integration

testing, where the focus is on design and the construction of the software
architecture.

• Taking another turn outward on the spiral, you encounter validation

testing, where requirements established as part of requirements modeling
are validated against the software that has been constructed.

• Finally, you arrive at system testing, where the software and other system
elements are tested as a whole.

• To test computer software, you spiral out in a clockwise direction along

streamlines that broaden the scope of testing with each turn..

14
Software Testing steps

15
• Unit testing
Software Testing steps
– tests focus on each component individually, ensuring that it
functions properly as a unit.
– Exercises specific paths in a component's control structure to
ensure complete coverage and maximum error detection
– Components are then assembled and integrated to form
complete software package.

• Integration testing
– addresses the issues associated with the dual problems of
verification and program construction.
– Focuses on inputs and outputs, and how well the
components fit together and work together .

16
• Validation testing
– Provides final assurance that the software meets all
functional, behavioral, and performance requirements.

• System testing
– Verifies that all system elements (software, hardware,
people, databases) mesh properly and that overall
system function and performance is achieved

17
Textbook
Software Engineering, A Practitioner’s
Approach- Roger S. Pressman,McGraw Hill
Edition, 6 th edition,2013(Chapter -13)

18