Slides 03.pdf

Software Quality Assurance
Software Testing Fundamentals
Slides 03
Software Testing Software Quality Assurance March 1, 2023 1 / 20

Agenda
1 Introduction
2 Some Basic Concepts
3 Software Testing Levels
4 Software Testing Methods
5 Software Testing Types

Introduction
Agenda
1 Introduction

Introduction
Software Testing
Software testing is a process, to evaluate the functionality of a
software application with an intent to find whether the developed
software met the specified requirements or not
Its purpose is to identify the defects to ensure that the product is
defect-free in order to produce a quality product
It is dynamic execution of software and the comparison of results of
that execution against a set of known, pre-determined criteria

Introduction
Software Testing life cycle
Figure: STLC

Some Basic Concepts
Agenda
1 Introduction

Some Basic Concepts
Software Testing vs Software Debugging

Some Basic Concepts
Software Debugging
Software Debugging is the process of finding, analyzing and removing
the causes of failures in a component or system

Some Basic Concepts
Debugging vs Testing
Objective
Responsibility
Automation
Knowledge

Some Basic Concepts
Some Basic Concepts
Validation vs Verification
Validation is the process of checking whether the specification captures
the customer’s needs (Are we building the right product?)
Verification is the process of checking that the software meets the
specification (Are we building the product right?)

Some Basic Concepts
Some Basic Concepts
Test Case
A Test case is a set of actions executed to verify a particular feature or
functionality of your software application
It is a set of preconditions, inputs, actions (where applicable), expected
results and postconditions, developed based on test conditions

Some Basic Concepts
Some Basic Concepts
Test Case Template/Elements can have following elements:
Test Suite ID
Test Case ID
Test Case Summary
Related Requirement
Prerequisites
Test Data
Expected Result
Actual Result
Status (Pass, Fail, or Deferred)
Test Environment
Date and time information

Some Basic Concepts
Some Basic Concepts
Test Suite is a collection of test cases which are organized in a
logical order

Some Basic Concepts
Some Basic Concepts
Defect Life Cycle, also known as Bug Life Cycle, is the journey of a
defect from its identification to its closure
Figure: Defect Life Cycle

Some Basic Concepts
Software Testing
Level = When to test
Method/Technique = How to test
Type = What to test

Software Testing Levels
Agenda
1 Introduction

Software Testing Levels – 1
1 Unit Testing
2 Integration Testing
3 System Testing
4 Acceptance Testing
Figure: Testing Levels

1 Unit Testing
A level of the software testing process where individual units of a
software are tested. The purpose is to validate that each unit of the
software performs as designed.
2 Integration Testing
A level of the software testing process where individual units are
combined and tested as a group. The purpose of this level of testing is
to expose faults in the interaction between integrated units

3 System Testing
A level of the software testing process where a complete, integrated
system is tested. The purpose of this test is to evaluate the system’s
compliance with the specified requirements
4 Acceptance Testing
A level of the software testing process where a system is tested for
acceptability. The purpose of this test is to evaluate the system’s
compliance with the business requirements and assess whether it is
acceptable for delivery

Software Testing Methods
Agenda
1 Introduction

Black Box Testing
White Box Testing
Gray-Box Testing
Manual Testing
Automated Testing

Black Box Testing
Figure: Black Box Testing
Black Box , also known as Behavioral Testing, is a software testing
method in which the internal structure/design/implementation of the
item being tested is not known to the tester

Black Box Testing
Black Box Testing method is applicable to the following levels of software
testing
Integration Testing
System Testing
Acceptance Testing

Black Box Testing
Types of Black Box Testing
Functional Testing
Tools that can be used are: QTP, Selenium
Non-Functional Testing
Tools that can be used are: LoadRunner, Jmeter
Regression Testing

Black Box Testing
Black Box Testing Techniques
Equivalence Partitioning
Boundary Value Analysis

Black Box Testing
Equivalence Partitioning
Equivalence partitioning strives to define a test case that uncovers
classes of errors, thereby reducing the total number of test cases that
must be developed
An equivalence class represents a set of valid or invalid states for
input conditions
Typically, an input condition is
A specific numeric value
A range of values
A boolean condition

Black Box Testing
Guidelines for Equivalence Classes
If an input condition specifies a range, one valid and two invalid
equivalence classes are defined
If an input condition specifies a member of a set, one valid and one
invalid equivalence class are defined
If an input condition is boolean, one valid and one invalid class are
defined

Black Box Testing
Equivalence Partitioning (Example)
Determine absolute of an integer
Two classes are formed
1 Positive integers
2 Negative integers
If an input condition is 0 < count < max
Three classes are formed
1 Valid inputs
2 Upper bound
3 Lower bound

Black Box Testing
Boundary Value Analysis (BVA)
Boundary value analysis (BVA) is a testing technique, which leads to
a selection of test cases that exercise bounding values
This is because, a greater number of errors tends to occur at the
boundaries of the input domain rather than in the “center”
BVA complements equivalence partitioning testing technique

Black Box Testing
Boundary Value Analysis (Example)
If range is 0.0 < x < 1
Valid inputs are 0.1, 0.9
Invalid inputs are 0, 1

White Box Testing
Figure: White Box Testing
White Box Testing (also known as Glass Box Testing and Structural
Testing) is a software testing method in which the internal structure/
design/ implementation of the item being tested is known to the
tester

White Box Testing
White Box Testing method is applicable to the following levels of software
testing
Unit Testing
Integration Testing
System Testing

White Box Testing
White Box Testing Techniques
Path testing
Loop testing
Condition testing

White Box Testing
Path testing
In this technique, control flow graphs are made from code or
flowchart and then Cyclomatic complexity is calculated which defines
the number of independent paths so that the minimal number of test
cases can be designed for each independent path
Figure: Flow Graph Notations

White Box Testing
Path testing – Cyclomatic Complexity
Basis path testing uses cyclomatic complexity, which is a software
metric that provides a quantitative measure of the logical complexity
of a program
When the cyclomatic complexity used in the context of the basis path
testing method, the value computed for cyclomatic complexity defines
the number of independent paths in the basis set of a program and
provides us with an upper bound for the number of tests that must be
conducted to ensure that all statements have been executed at least
once

White Box Testing
Cyclomatic Complexity Example
1 while i < n − 1 do
2 while j < n do
3 if A[i] < A[j] then
4 swap(A[i], A[j])
5 end
6 i ← i + 1
7 end
Figure: Flow Graph
V (G) = (Number of edges)−(Number of Nodes)+2 = 9−7+2 = 4
V (G) = P + 1 = 3 + 1 = 4
P = Number of predicate nodes (node that contains condition)

White Box Testing
Loop testing
Loops are widely used and these are fundamental to many algorithms
hence, their testing is very important. Errors often occur at the
beginnings and ends of loops
For simple loops of size n, test cases are designed that:
Skip the loop entirely
Only one pass through the loop
2 passes
m passes, where m < n
(n − 1), n, and (n + 1) passes through the loop

White Box Testing
Loop testing
For nested loops, all the loops are set to their minimum count and we
start from the innermost loop. Simple loop tests are conducted for
the innermost loop and this is worked outwards till all the loops have
been tested
If the loops are independent of one another
then treat each as a simple loop
else treat as nested loops
for example, the final loop counter value of loop 1 is used to initialize
loop 2

White Box Testing
Condition testing
we will test all logical conditions for both true and false values; that
is, we will verify for both if and else condition

Manual Testing vs Automated Testing
Manual Testing
It is a method of testing whereby software is tested manually (by a
human). The tester does not use any script or tool to assist in testing
Automated Testing
It is a method of testing whereby software is tested with the help of
scripts and tools

Software Testing Types
Agenda
1 Introduction

Functional Testing
Non-Functional Testing
Performance Testing
Usability Testing
Regression Testing
Smoke Testing
Alpha Testing
Beta Testing

Slides 03.pdf

Recommended

Recommended

More Related Content

Similar to Slides 03.pdf

Similar to Slides 03.pdf (20)

Recently uploaded

Recently uploaded (20)

Slides 03.pdf