You are on page 1of 18

Categories of Test Design

Techniques
Experience Based Technique

Kamna Srivastava (A1004918030)


Anjani Rani (A1004918043)
- Test design is the process of deriving test cases from test conditions.

- Test condition is a general idea of anything that we need to verify.

- Test cases consist of pre-conditions, the inputs, actions, expected results, post-
conditions, etc.
Types Of Test Design Techniques
Static Testing Technique
- The static testing design technique is made use of
even before executing the code.
- It checks the documents like requirement
specification, functional specification, design
specification etc.
- It may also check the source code.
- Static Analysis is a type of tool-supported static
testing that checks whether the source code adheres
to industry standards.
Examples include reviewing - walk through, inspection etc.
Static Analysis By Tools
Following are the types of defects found during static analysis:

- A variable with an undefined value


- Inconsistent interface between modules and components
- Variables that are declared but never used
- Unreachable code (or) Dead Code
- Programming standards violations
- Security vulnerabilities
- Syntax violations
Specification Based Testing Technique
This technique uses the specification of the program (or
some other kind of model of what the system should do) as
the point of reference for test data selection.

A specification can be anything like a written document,


collection of use cases, a set of models or a prototype.
Types Of Specification Based Techniques
Equivalence partitioning: Divides the input data of a software unit into partitions of
equivalent data from which test cases can be derived.

Boundary value analysis: Tests are designed to include representatives of boundary


values in a range.

Decision tables: Tests are more focused on business logic or business rules. A decision
table is a good way to deal with combinations of inputs.

State Transitioning: Used when the system is defined in terms of a finite number of states
and the transitions between the states is governed by the rules of the system.
Examples
Decision Table based testing Boundary Value Analysis
The condition states that if the user provides the correct Input condition is valid between 1 to 10
username and password, the user will be redirected to the
homepage. Boundary values : 0,1,2 and 9,10,11

If any of the input is wrong, an error message will be


displayed.

Conditions Rule 1 Rule 2 Rule 3 Rule 4

Username F F T T

Password F T F T

Output Error Error Error Homepage


- Structure-based techniques serve two Test
purposes: test coverage measurement and Coverage
structural test case design. Measurement

- The structure-based or white-box technique


design test cases based on the internal
structure of the software. Structure
- This technique exhaustively tests the
Based
developed code. Techniques
- Developers who have complete information
of the software code, its internal structure,
and design help to design the test cases.
Structural
Test Case
Design
This technique is further divided into five categories:

Statement
L
Testing & Condition
Coverage All Path
Testing
Testing
Decision Multiple
Testing Condition
Coverage Testing
Example
Read X
Read Y
IF X+Y > 100 THEN
Print “Large”
ENDIF
If X > 50 THEN
Print “X Large”
ENDIF

● Nodes represent statement of code [E.g.: entry, exit,


decisions]
● Edges represent links between nodes
Statement Coverage

If X=55

Y=69

Then X+Y>100 “Yes”

Traversing path = A1-B2-C4-5-D6-E8

Statement Coverage (SC) = 1

In case of “No”

Traversing path = A1-B3-5-D7


- The experience-based testing technique is defining
the test cases based on the experience of the people
involved in testing.

- The experience involves the skills and background


of the tester.

- The previous experience in similar projects helps


them to analyze the system better for designing the
test cases from test conditions.

- The testing technique is particularly useful when


there is a lack of adequate specifications.
When Experience Based
Technique Is Required ?

- Non-availability of requirements and specifications.


- Limited Knowledge of the Software product.
- Inadequate specification
- Restricted amount of time, to perform testing.
Techniques Of Experience Based Testing

Lorem ipsum dolor sit amet, Lorem ipsum dolor sit amet,
Error
consecteturGuessing
adipiscing. Lorem Exploratory
consectetur adipiscing. Lorem
ipsum dolor sit. ipsum dolor sit.
Techniques Techniques
20XX 20XX

20XX 20XX

Lorem ipsum dolor sit amet, Lorem ipsum dolor sit amet,
Checklist Based
consectetur adipiscing. Lorem
Attack Testing
consectetur adipiscing. Lorem
ipsum dolor sit. ipsum dolor sit.
Testing

LOREM
Thank you

You might also like