ATDD in Legacy Code: catch regression bugs before production — in banking, insurance, and healthcare systems.
Hands-on work with your teams. Limited spaces for 2027.
📅 Join our next live courses: ATDD, Clean Architecture, Pipelines
Early bird: €100 off with code EARLYBIRD100
👋 Hello, this is Valentina with the free edition of the Optivem Journal. I help Engineering Leaders & Senior Software Developers apply TDD in Legacy Code.
“AI can write the tests.”
Finally.
All those tests nobody has time to write.
No more days spent waiting for manual QA before every release.
Six months later…
More code.
More PRS.
But releases aren’t faster.
QA is still testing everything manually before anything ships — exactly as they were last year.
And the bugs? Still there.
Now management wants to know:
What did we actually get for the money?
You have plenty of numbers to show them.
More code.
More PRs.
More tests.
But none of those numbers answer the question.
Because more code isn't the same as safer releases.
AI copies whatever it finds
Ask AI to write a test.
But what if your e2e suite is full of tests coupled to the UI?
Click the button.
Fill the field.
Check the screen.
AI just writes hundreds more tests like that.
Faster.
It doesn't stop and ask:
“Is this a good way to test this application?”
It looks at the tests you already have and learns:
“This is how tests are written here.”
You had a speed limit
Before AI, writing tests was slow.
That was annoying.
But it also limited how many bad tests you could create.
Your team could only write so many brittle E2E tests before the sprint ended.
AI removed that limit.
Now you can write hundreds in the time it used to take to write a few.
But the tests aren’t any better.
They’re still coupled to the UI.
Still break when the UI changes.
Still create more work for the team.
Before AI writes 100 more tests
AI writing tests isn’t the problem.
AI writing bad tests faster is.
The problem is giving it a bad test suite to learn from.
❌ If your tests are all coupled to the UI, AI will keep generating tests like:
click("Place Order")
✅ Instead, fix the test, so that it's coupled to the domain rather than the UI:
shop.placeOrder()
Now AI can do what it’s good at:
Write hundreds more. Fast.
⚡Join our next live courses
Early bird: €100 off with code EARLYBIRD100
ATDD in Legacy Code: catch regression bugs before production — in banking, insurance, and healthcare systems.
Hands-on work with your teams. Limited spaces for 2027.
AI just looks at your existing tests and writes more of the same.