QA Evangelist » Blog Archive » Equivalence Partition Testing/Boundary testing

Equivalence Partition Testing/Boundary testing

A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes . Both input data and output results can be partitioned into equivalence classes. If 2 test cases are expected to have the same test result, they are considered equivalent. The steps for designing the test cases are:
1) Divide input or outputs into equivalence classes
2) (Usually) Choose 1-2 test cases from each equivalence class.
3) The boundary cases or the extreme values are normally the ones that cause failure – boundary testing. All outputs should be considered when analyzing program boundaries. The inputs for the output boundary values should be considered in the test cases.
4) Input boundary values might not generate output boundary values.

Leave a Comment