Assignment 6
Equivalence Class Testing – Online Pizza Booking System
Objective
To apply Equivalence Class Testing (ECT) by identifying valid and invalid input
classes for an online pizza booking system and designing optimized test cases using
representative values.
Task 1: Identify Equivalence Classes
Equivalence classes divide input data into valid and invalid groups where the
system should behave similarly.
1. Pizza Size
Allowed values: S, M, L
Class
Equivalence Class Description
Type
Valid pizza
Valid Class S, M, L
sizes
Invalid Other values (A, X, 1, Invalid pizza
Class empty) sizes
2. Number of Pizzas
Valid range: 1–10
Class Equivalence
Description
Type Class
Acceptable
Valid Class 1–10
quantity
Invalid
≤0 Too few pizzas
Class
Invalid
>10 Too many pizzas
Class
3. Extra Toppings
Valid range: 0–5
Class Equivalence
Description
Type Class
Valid toppings
Valid Class 0–5
count
Invalid Negative
<0
Class toppings
Invalid Too many
>5
Class toppings
Task 2: Representative Values
Representative values are selected from each equivalence class.
Representative
Input Class
Value
Pizza
Valid M
Size
Pizza
Invalid X
Size
Quantity Valid 3
Invalid
Quantity 0
(Low)
Invalid
Quantity 11
(High)
Toppings Valid 2
Invalid
Toppings -1
(Low)
Invalid
Toppings 6
(High)
Task 3: Optimized Test Cases
TC Pizza Quanti Toppin Expected
ID Size ty gs Result
TC1 M 3 2 Order Placed
Invalid Pizza
TC2 X 3 2
Size
TC3 S 0 2 Invalid
TC Pizza Quanti Toppin Expected
ID Size ty gs Result
Quantity
Invalid
TC4 L 11 2
Quantity
Invalid
TC5 M 3 -1
Toppings
Invalid
TC6 M 3 6
Toppings
Justification of Equivalence Classes
1. Pizza Size
o Valid inputs: S, M, L should all behave similarly (system accepts order).
o Any other value should be rejected.
2. Quantity
o Valid range: 1–10 allows reasonable number of pizzas.
o Values outside this range should be rejected.
3. Extra Toppings
o Valid range: 0–5 toppings.
o Negative or excessively large values should be rejected.