Boundary analysis techniques are used to create test cases that divide equivalence partitioned groups.

Equivalence partitioning (EP) first divides the input (or output) space into classes that are expected to exhibit similar behaviour. Boundary value analysis (BVA) is then applied to those already-defined partitions to derive the specific test cases that exercise the values at, just below, and just above the boundaries that separate one equivalence class from the next. Thus BVA is indeed “used to create test cases that divide (i.e., lie on the dividing lines between) equivalence-partitioned groups.”

Why the other option (False) is wrong:

Saying “False” would imply that boundary analysis is unrelated to, or not used after, equivalence partitioning. Authoritative testing literature consistently presents BVA as a complementary step that refines EP by focusing on the partition boundaries; therefore dismissing this relationship would contradict the established definition and recommended practice.

1. Myers, G. J., Sandler, C., Badgett, T. “The Art of Software Testing,” 2nd ed., Wiley, 2004.

• Chap. 4 “Equivalence Class Partitioning and Boundary-Value Analysis,” pp. 54-57 – describes BVA as an extension of EP used to select test cases at the borders of equivalence classes.

2. Ammann, P., Offutt, J. “Introduction to Software Testing,” 2nd ed., Cambridge Univ. Press, 2017.

• Sect. 5.4 “Boundary Value Analysis,” pp. 139-140 – states that after partitions are defined, boundary tests are chosen at the edges between classes. DOI: 10.1017/9781108135571

3. Stanford University, CS253 “Software Testing” course notes (Spring 2020).

• Lecture 5 slides 9-11 – illustrate EP followed by BVA; boundaries are where test cases are created to separate partitions.