Twelve Days of Christmas - Tester version

🙋 Questions
,
1

Here’s my version. What would you have in yours?

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.

Ady Stokes on LinkedIn: The Twelve Days of testing   On the first day of Christmas, testing gave…?

8 Likes
2

The Twelve Days of Testing

(to the tune of “The Twelve Days of Christmas”)

On the first day of testing, my QA gave to me:

A bug in the prod API.

On the second day of testing, my QA gave to me:

Two missing semicolons,

And a bug in the prod API.

On the third day of testing, my QA gave to me:

Three broken buttons,

Two missing semicolons,

And a bug in the prod API.

On the fourth day of testing, my QA gave to me:

Four endless spinners,

Three broken buttons,

Two missing semicolons,

And a bug in the prod API.

On the fifth day of testing, my QA gave to me:

Fiiiiive failing builds!

Four endless spinners,

Three broken buttons,

Two missing semicolons,

And a bug in the prod API.

On the sixth day of testing, my QA gave to me:

Six null exceptions,

Fiiiiive failing builds!

Four endless spinners,

Three broken buttons,

Two missing semicolons,

And a bug in the prod API.

On the seventh day of testing, my QA gave to me:

Seven logs not logging,

Six null exceptions,

Fiiiiive failing builds!

Four endless spinners,

Three broken buttons,

Two missing semicolons,

And a bug in the prod API.

On the eighth day of testing, my QA gave to me:

Eight features crashing,

Seven logs not logging,

Six null exceptions,

Fiiiiive failing builds!

Four endless spinners,

Three broken buttons,

Two missing semicolons,

And a bug in the prod API.

On the ninth day of testing, my QA gave to me:

Nine broken configs,

Eight features crashing,

Seven logs not logging,

Six null exceptions,

Fiiiiive failing builds!

Four endless spinners,

Three broken buttons,

Two missing semicolons,

And a bug in the prod API.

On the tenth day of testing, my QA gave to me:

Ten typos lurking,

Nine broken configs,

Eight features crashing,

Seven logs not logging,

Six null exceptions,

Fiiiiive failing builds!

Four endless spinners,

Three broken buttons,

Two missing semicolons,

And a bug in the prod API.

On the eleventh day of testing, my QA gave to me:

Eleven flaky tests,

Ten typos lurking,

Nine broken configs,

Eight features crashing,

Seven logs not logging,

Six null exceptions,

Fiiiiive failing builds!

Four endless spinners,

Three broken buttons,

Two missing semicolons,

And a bug in the prod API.

On the twelfth day of testing, my QA gave to me:

Twelve deadlines shifting,

Eleven flaky tests,

Ten typos lurking,

Nine broken configs,

Eight features crashing,

Seven logs not logging,

Six null exceptions,

Fiiiiive failing builds!

Four endless spinners,

Three broken buttons,

Two missing semicolons,

And a bug in the prod API.

1 Like