Can we use a mock to unblock a dependency?
Controlled provisional interfaceA mock can support learning and parallel work when its assumptions and limits are explicit. It does not prove the real integration works, so plan verification against the actual dependency.
What to do now
- Define the provisional interface behavior
- Record assumptions and known gaps
- Use the mock for suitable work
- Schedule real integration and reconciliation tests
When to escalate
Escalate when
The team proposes release based only on mocked behavior.
Who decides
The accountable integration or dependency owner
Example
A team develops against a mock payment response but verifies actual provider behavior before launch.
Mistake to avoid
Treating a successful mock test as production integration evidence.
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
- How do we prevent interface changes during final testing?Interface stabilization gap
- A shared API changes without notice. What should happen?Uncontrolled interface change
- The project needs an integration, but the API has no documentation. How should we estimate?Unknown interface effort
- An issue has been waiting for a decision for weeks. How do we unblock it?Decision queue blockage