How do we prevent interface changes during final testing?
Interface stabilization gapAgree a controlled interface baseline for the relevant test period and a clear exception process. Necessary changes remain possible, but their effect on completed verification must be assessed.
What to do now
- Identify interfaces under final verification
- Confirm versions and change boundaries
- Route necessary exceptions explicitly
- Repeat affected tests after approved changes
When to escalate
Escalate when
A change invalidates critical evidence without time to reverify.
Who decides
The accountable integration or dependency owner
Example
A final test cycle records API and schema versions and reruns affected cases after a required correction.
Mistake to avoid
Calling an interface frozen while allowing undocumented updates.
Prevent a repeat
Verify dependency completion with the consuming team and test the integrated outcome early enough to act.
Suggested ApprovedFlow setup
- Tasks
- Documents
- Projects
Keep dependency owners, required evidence and dates with linked work records, confirming supported link behavior in the current build. See the platform
Related cases
- Can we use a mock to unblock a dependency?Controlled provisional interface
- A shared API changes without notice. What should happen?Uncontrolled interface change
- A critical vulnerability appears during the final project week. What should I prioritize?Release-time vulnerability risk
- A requirement changed after testing began. How do we handle it?Late requirement change