A license-renewal producer plans to remove a field that independently deployed consumers still need. What test order protects those consumers?
Select an answer to reveal the explanation.
Short Explanation
Put the old handshake in a test that must stay green. If the producer breaks that handshake, the test fails before production does. Versioning is the escape hatch—not skipping the test.
Full Explanation
Backward-compatible contracts are enforced by tests: consumer expectations or schema checks that still pass against the old producer will fail when the producer removes a required field. That order protects independently deployed consumers. Creating a new API version is the deliberate escape hatch for incompatible change; removing a field first and fixing tests later is not.