This document discusses various software testing techniques including: - Equivalence partitioning which divides input data into equivalent classes to reduce the number of test cases. - Boundary value analysis which tests at the boundaries of input domains to identify errors. - Decision table testing which deals with combinations of inputs and outputs through a table. - State transition diagrams which define a system by its states and transitions between states based on rules. - Use case testing which identifies test cases by describing how actors use the system from start to finish. Examples are provided to illustrate each technique.

1. Prepared by:
Mona M. Abd El-Rahman.
QC Engineer at Ibtikar Technologies Co.
Part 2

2. Acceptance
System
Integration
Component Test

3. Testing
Static
Reviews
Dynamic
Functional
Non-
Functional
Performance Security Usability

4. Design
Techniques
Equivalence
Partitioning
Boundary
Value
Analysis
Decision
Table
Testing
State
Transition
Diagram
Use case
Testing

5. • Definition: A software testing technique that
divides the input data of a software unit into
partitions of equivalent data from which test
cases can be derived.
• Advantage: It reduces the time required for
performing testing of a software due to less
number of test cases.
Equivalence Partitioning:

6. • It’s widely recognized that input values at the
extreme ends of input domain cause more
errors in system. More application errors
occur at the boundaries of input domain.
• It is used to identify errors at boundaries
rather than finding those exist in center of
input domain.
Boundary Value Analysis:

7. Example:
Tax Calculation:
From To %
0 1200 0
Over 1200 Up to 3000 5
Over 3000 10

8. • Definition: Decision Table Testing is a good
way to deal with a combination of inputs,
which produce different results.
• Advantage: It helps reduce test effort in
verifying each and every combinations of test
data, at the same time ensuring complete
coverage.
Decision table testing:

9. Conditions Rule 1 Rule 2 Rule 3 Rule 4
Cond.1
Cond.2
Actions
Act.1
Act.2

10. How to ensure complete coverage ?
2 𝑛
N: Number of conditions

11. Example:
New tax will be applied depending on the following conditions:
o Income less than 1200, not married and younger than 35 
Tax=15%.
o Income less than 1200, married and younger than 35  Tax =
10%.
o Income less than 1200, married and older than 35  Tax = 5%.
o Else 15%.

12. 1 2 3 4 5 6 7 8
Less
then
1200
T T T T F F F F
Marrie
d
T T F F T T F F
Less
than
35
T F T F T F T F
15 T T T T T T
10 T
5 T

13. State transition technique is a dynamic testing
technique, which is 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.
State Transition Diagram:

14. State 1
State 2
Transition
Input
ActionEvent Output

15. How to determine coverage level?
N-switch
N = 0  Start – End – Start
N = 1  Start – End – Start - End

16. Example:
- A simple electronic clock has for mode, display
time, change time, display date and change date.
- The change mode button change between
display time and display date.
- The reset button switch from display time to
adjust time or display date to adjust date.
- The set button returns from adjust time to
display time or adjust date to display date.

17. • Definition: A use case is a description of a
particular use of the system by an actor or
user.
• Use: It is used widely in developing tests at
system or acceptance level.
• Advantage: It helps identifying test cases that
cover the entire system, on a transaction by
transaction basis from the start to finish.
Use case testing:

18. Actor
Case 1
Case 2
Case3

19. Example:
ATM PIN

20. For any questions, feel free to contact me
mona.m.abdelrahman@gmail.com