Tests and a rollback plan before anyone touches the old code
We add tests that pin down how the system works today, error monitoring and a way to roll back every release. Only then do changes stop being risky.
What we add before the first change
The same steps for every system, whatever the technology.
- 1Characterization testsWe record what the system does today for typical and unusual data. The test doesn't judge whether that's right; it makes sure it doesn't change by accident.
- 2MonitoringWe collect errors, response times and key business events, such as orders per hour.
- 3Rollback planEvery release can be rolled back with one command, database changes included.
- 4A production copy for testingAn environment with production-like data where we check changes before release.
Signs you're missing a safety net
No releases on Fridays
Customers report the bugs
No tests
A rollback takes all day
The tools we use
We pick them to suit the system and what the team already knows.
Tests
Error monitoring
Metrics
Deployments
Database migrations
Backups
How we check the safety net works
We measure how often you ship, how many releases need rolling back and how quickly you know about an error.
- 1Key paths covered by tests
- 2Releases per month
- 3Rolled-back releases
- 4Time from error to alert
We only count a backup as working once a restore from it has succeeded.
Common questions
Do tests make sense for old code?
Yes. Characterization tests don't require restructuring the code. They capture its current behaviour so every change shows up.
Won't this slow the modernization down?
At the start, yes, but later changes go faster because the team stops fearing releases.
Can we order just the safety net?
Yes. It's a good first step even if you decide on further modernization later.
Who maintains the tests?
Your team, or us under a maintenance package. Tests and docs stay in your repository.
Tell us what you're afraid to touch
Let us know what the system runs on, how releases work today and what broke recently. We reply within one business day.