Exp 9 and 10 SE LAb
Exp 9 and 10 SE LAb
Exp 9 and 10 SE LAb
Equivalence class partitioning is a software testing technique that divides the input domain of
a program into classes of equivalent inputs. Each class represents a set of inputs that should
produce the same output from the system under test.
Input Parameters: e user inputs, configuration settings, or any other relevant data.
Equivalence Classes: Divide the possible values of each input parameter into equivalence
classes. An equivalence class is a set of inputs that should produce the same output and are
likely to exhibit similar behavior from the system. The equivalence classes should cover both
valid and invalid inputs.
Representative Values: Choose representative values from each equivalence class to create
test cases. These values should adequately represent the behavior of the entire class.
Test Cases: For each input parameter, create test cases that cover different combinations of
values from their respective equivalence classes. Ensure that you include both boundary
values and values from the middle of each range.
Execute Test Cases: Execute the designed test cases on the system under test and observe the
outputs. Compare the actual outputs with expected outputs to determine if the system behaves
as expected.
Evaluate Coverage: Assess the coverage achieved by the test suite by analyzing how many
equivalence classes have been tested and how thoroughly they have been covered. Adjust the
test suite as necessary to improve coverage.
Here's a simplified example to illustrate the process:
Scenario: Testing a login system with two input parameters: username and password.
Input Parameters: Determine the input parameters or variables that have boundaries that need
to be tested.
Boundary Values: For each input parameter, identify the boundaries and determine the values
immediately before and after those boundaries. These values are the focus of boundary value
analysis.
Test Cases: Create test cases that cover the boundary values identified in step 2. Each test
case should test one boundary value at a time, focusing on the transitions from one state to
another.
Additional Test Cases: In addition to the boundary values, include test cases for values just
inside and just outside the boundary values. This ensures thorough testing of the system's
behaviour around the boundaries.
Execution Test Cases: Execute the designed test cases on the system under test and observe
the behaviour at the boundaries.
Evaluate Coverage: Assess the coverage achieved by the test suite by analyzing how many
boundary values have been tested and how thoroughly they have been covered. Adjust the
test suite as necessary to improve coverage.
Here's a simplified example to illustrate the process:
Scenario: Testing a system that calculates the area of a rectangle based on its length and
width.