Replay an older event into the new consumer
Historical messages exercise assumptions that fresh test fixtures miss. Test their final effects before relying on replay as a recovery tool.
Read articleCobnex blogs / Global
Cobnex blog
AI implementation, software architecture and cloud operations for teams worldwide.
456 articles
Page 7 of 26
Pause a reader between its database read and cache write
A controlled interleaving can reproduce stale repopulation reliably. Ordinary load tests often miss this short but important race.
Read articleRehearse the migration while a long transaction is open
A fast command on a quiet database can wait behind live work. Test lock contention and cancellation before the release window.
Read articleMake two requests compete for the last place
A deterministic race test proves the capacity rule more clearly than a large burst of requests that may never overlap at the critical point.
Read articleRehearse rollback after the target accepts a write
The difficult recovery case begins when the new environment contains data the old one does not. Test that boundary explicitly.
Read articleTest a denied deployment before a team needs an exception
A platform control should fail clearly and preserve a usable recovery path. Exercise both legitimate restrictions and accidental policy conflicts.
Read articleRestore a point before the bad change
Recovery from corruption requires more than choosing the newest backup. Rehearse how to identify a clean point and account for legitimate work after it.
Read articleSimulate a network partition, not only a stopped server
The harder failover case is an old region that some clients can still reach. Test how the design prevents conflicting writes under partial visibility.
Read articleChange one safe resource outside the deployment pipeline
A controlled drift exercise should prove detection, investigation and reconciliation. Stopping at an alert leaves the most consequential part untested.
Read articleMake the canary fail before trusting automatic promotion
Test the release controller with bad results, missing results and a healthy control group. The exercise should prove the decision path, not just deployment mechanics.
Read articleBreak the workflow while leaving the health endpoint green
A controlled dependency failure can show whether monitoring detects user impact or only process availability.
Read articleRemove an ownership tag and follow the charge
Missing metadata should produce visible unresolved cost. Test that it does not disappear from totals or get silently assigned to the wrong team.
Read articleKeep one worker on the old credential during the drill
A delayed consumer reveals whether rotation depends on every process updating at once. Test its recovery after the previous credential is no longer usable.
Read articleLose the Xero response after the test invoice is created
Reproduce an unknown outcome in a safe organisation. The integration should recover the original result rather than create another invoice automatically.
Read articleEdit the same contact in both systems before sync runs
A controlled conflict shows whether ownership rules survive real timing. Verify the chosen value and the evidence retained for the losing change.
Read articleDeliver the same webhook while the first worker is still running
Concurrent duplicates expose gaps that sequential retries miss. Verify receipt deduplication and the actual business effect independently.
Read articleThrottle one account while another keeps working
A scoped failure test shows whether shared workers preserve fairness. The unaffected account should continue within its own provider budget.
Read articleReplay a failed command after the record has changed
Recovery must respect current business state. Test a delayed command against a newer revision before allowing broad replay.
Read article