The Twelve Days of testing
12 Dec 2025
The Twelve Days of testing
On the first day of Christmas, testing gave to me. A bug that delayed release.
On the second day of Christmas, testing gave to me. Two testing tools and a bug that delayed release.
On the third day of Christmas, testing gave to me. Three flaky tests. Two testing tools and a bug that delayed release.
On the fourth day of Christmas, testing gave to me. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
On the fifth day of Christmas, testing gave to me. Five crucial risks. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
On the sixth day of Christmas, testing gave to me. Six bugs resolved. Five crucial risks. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
On the seventh day of Christmas, testing gave to me. Seven backlog items. Six bugs resolved. Five crucial risks. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
On the eighth day of Christmas, testing gave to me. Eight hours debugging. Seven backlog items. Six bugs resolved. Five crucial risks. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
On the ninth day of Christmas, testing gave to me. Nine bugs in live. Eight hours debugging. Seven backlog items. Six bugs resolved. Five crucial risks. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
On the tenth day of Christmas, testing gave to me. Ten testing charters. Nine bugs in live. Eight hours debugging. Seven backlog items. Six bugs resolved. Five crucial risks. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
On the eleventh day of Christmas, testing gave to me. Eleven testers testing. Ten testing charters. Nine bugs in live. Eight hours debugging. Seven backlog items. Six bugs resolved. Five crucial risks. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
On the twelfth day of Christmas, testing gave to me. Twelve product demos. Eleven testers testing. Ten testing charters. Nine bugs in live. Eight hours debugging. Seven backlog items. Six bugs resolved. Five crucial risks. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
On the first day of Christmas, testing gave to me. A bug that delayed release.
On the second day of Christmas, testing gave to me. Two testing tools and a bug that delayed release.
On the third day of Christmas, testing gave to me. Three flaky tests. Two testing tools and a bug that delayed release.
On the fourth day of Christmas, testing gave to me. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
On the fifth day of Christmas, testing gave to me. Five crucial risks. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
On the sixth day of Christmas, testing gave to me. Six bugs resolved. Five crucial risks. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
On the seventh day of Christmas, testing gave to me. Seven backlog items. Six bugs resolved. Five crucial risks. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
On the eighth day of Christmas, testing gave to me. Eight hours debugging. Seven backlog items. Six bugs resolved. Five crucial risks. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
On the ninth day of Christmas, testing gave to me. Nine bugs in live. Eight hours debugging. Seven backlog items. Six bugs resolved. Five crucial risks. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
On the tenth day of Christmas, testing gave to me. Ten testing charters. Nine bugs in live. Eight hours debugging. Seven backlog items. Six bugs resolved. Five crucial risks. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
On the eleventh day of Christmas, testing gave to me. Eleven testers testing. Ten testing charters. Nine bugs in live. Eight hours debugging. Seven backlog items. Six bugs resolved. Five crucial risks. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
On the twelfth day of Christmas, testing gave to me. Twelve product demos. Eleven testers testing. Ten testing charters. Nine bugs in live. Eight hours debugging. Seven backlog items. Six bugs resolved. Five crucial risks. Four test cases. Three flaky tests. Two testing tools and a bug that delayed release.
Ady Stokes
Freelance Consultant
He / Him
MoT Ambassador. Currently semi-retired and freelancing. I am, amongst other things, a writer, speaker, and accessibility advocate. Leeds Chapter Lead. MoT Certs curator and article editor for MoT and WonderProxy. Testing wisdom, friendly, testing songs and poems. Great minds think differently. STEC and SQEC Certified.
Open To
Write
Teach
Speak
Meet at MoTaCon 2026
Podcasting
Review Conference Proposals
Judy Mosley
This is wonderful!
Sign in
to comment
ACCELQ self-healing automation adapts to UI changes, cutting maintenance by 72%. Book a Demo to see it on your site.
Explore MoT
What I learned about influence by becoming a stakeholder
Boost your career in software testing with the MoT Software Testing Essentials Certificate. Learn essential skills, from basic testing techniques to advanced risk analysis, crafted by industry experts.
Into the MoTaverse is a podcast by Ministry of Testing, hosted by Rosie Sherry, exploring the people, insights, and systems shaping quality in modern software teams.
