What is equivalence testing in the context of wca4z validation?
Select an answer to reveal the explanation.
Short Explanation
Equivalence testing means running the same production-representative inputs through the COBOL and Java versions and comparing outputs. If the outputs match, you know the transformation preserved behavior. On real mainframe exams, this concept comes up repeatedly, so lock it in.
Full Explanation
Equivalence testing runs identical production-representative inputs through the COBOL and Java versions and compares outputs, proving behavior was preserved. The dependency-graph display, public-method count, and TCP-port alignment options are wrong because they check tooling, structure, or deployment, not functional output equivalence.