Testing Techniques
Testing Techniques
Order Pizza:
Here is the test condition
1. Any Number greater than 10 entered in the Order Pizza field(let say
11) is considered invalid.
2. Any Number less than 1 that is 0 or below, then it is considered
invalid.
3. Numbers 1 to 10 are considered valid
4. Any 3 Digit Number say -100 is invalid.
We cannot test all the possible values because if done, the number of
test cases will be more than 100. To address this problem, we use
equivalence partitioning hypothesis where we divide the possible values
of tickets into groups or sets as shown below where the system behavior
can be considered the same.
The divided sets are called Equivalence Partitions or Equivalence
Classes. Then we pick only one value from each partition for testing. The
hypothesis behind this technique is that if one condition/value in a
partition passes all others will also pass. Likewise, if one condition in
a partition fails, all other conditions in that partition will fail.
That means results for values in partitions 0-5, 6-10, 11-14 should be
equivalent
Enter Password:
Expected
Test Case # Test Case Description
Outcome
System should
1 Enter 0 to 5 characters in password field
not accept
System should
2 Enter 6 to 10 characters in password field
accept
System should
3 Enter 11 to 14 character in password field
not accept
Examples 3: Input Box should accept the Number 1 to 10
Here we will see the Boundary Value Test Cases
The condition is simple if the user provides the correct username and
password the user will be redirected to the homepage. If any of the input
is wrong, an error message will be displayed.
Username (T/F) F T F T
Password (T/F) F F T T
Output (E/H) E E E H
Legend:
T – Correct username/password
F – Wrong username/password
E – Error message is displayed
H – Home screen is displayed
Interpretation:
S1) Start S2 S2