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
STEC Certified. MoT Ambassador, writer, speaker, accessibility advocate. Consulting, Leeds Chapter Lead. MoT Certs curator. Testing wisdom, friendly, songs and poems. Great minds think differently
Judy Mosley
This is wonderful!
Sign in
to comment
Create E2E tests visually. Get clear, readable YAML you can actually maintain.
Explore MoT
Tue, 17 Mar
Thunders Connect – Mar 17, Station F, Paris: QA & testing future, certification, product updates, panel, Station F tour & first-ever Thunders Awards. RSVP if in Paris!
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.
