Question 650
A pricing procedure passes compile checks but calculates tax incorrectly at zero quantity and high precision. Which implementation step most directly addresses this requirement?
Explanation
Correct Answer
SQL unit tests should exercise business invariants and boundary behavior beyond compilation. Add isolated tests for rounding, negative inputs and expected failures. Tests catch the incorrect calculation before merge and pass after correction.
Incorrect Answers
The UI screenshot does not exercise high-precision tax arithmetic or expected database error behavior.
Self-comparison can preserve the same billing bug; tests need independently determined expected outputs.
Shared-state tests can contaminate later results and obscure whether errors leave durable unintended records.