How should a team establish that COBOL logic transformed into Java still behaves correctly?
Select an answer to reveal the explanation.
Short Explanation
Run the transformed code against the same inputs and compare the results to the legacy behavior. Reading the code only tells you what someone intended, not what it actually does.
Full Explanation
Equivalence is a claim about behavior, so it is established by executing both the expected legacy behavior and the transformed code against the same inputs and comparing outcomes. The approach of reading the generated Java carefully is incorrect because reading catches obvious mistakes but cannot find the subtle numeric, rounding, and edge-case differences that matter most in transformed business logic. The approach of starting the transformed service and treating a clean startup as evidence is incorrect because starting successfully proves the service initializes, not that any calculation is right. The approach of capturing screenshots before and after and comparing them visually is incorrect because screenshots compare presentation and cannot assert on the data effects underneath. For the exam, tie validation to executed comparative tests.