Spent hoursdebuggingonly to find itwas a typo.Rejected adeveloper's"It's not a bug;it's a feature"excuse.Conducteda knowledgesharingsession.Disabled atest“temporarily”— 3 monthsago.Found abug inproduction.UsedChatGPT orStackOverflow to fixa test failure.Ran thesame testmultipletimes just tomake sure.Watched adeveloper fixone bug andintroducetwo more.Wrotea flakytest.Used thephrase, "Itworks on mymachine."Filed a bug,only to realizeit was alreadyin the backlogsince last year.Ticket movedback andforth betweenQA and Deva few times.Discoveredan edgecase no onethought of.Helped adeveloperreproduce abug theycouldn’t see.Improved thetest processfor the wholeteam.Discovered aperformanceissue duringload testing.Got ashoutout in ateammeeting forgreat testing.Automated atask andsaved hoursof manualeffort.Had a test failbecause oftimezone orlocalizationissues.Preparedsomethingfor QAonsite.Skipped techdebt days tofinish anurgent ticket.Wrote a testcase for acompletelyunrealisticscenario.Answeredto a requestin supportchannel.Had to clarifythat QAdoesn’t “ownqualityalone.”Spent hoursdebuggingonly to find itwas a typo.Rejected adeveloper's"It's not a bug;it's a feature"excuse.Conducteda knowledgesharingsession.Disabled atest“temporarily”— 3 monthsago.Found abug inproduction.UsedChatGPT orStackOverflow to fixa test failure.Ran thesame testmultipletimes just tomake sure.Watched adeveloper fixone bug andintroducetwo more.Wrotea flakytest.Used thephrase, "Itworks on mymachine."Filed a bug,only to realizeit was alreadyin the backlogsince last year.Ticket movedback andforth betweenQA and Deva few times.Discoveredan edgecase no onethought of.Helped adeveloperreproduce abug theycouldn’t see.Improved thetest processfor the wholeteam.Discovered aperformanceissue duringload testing.Got ashoutout in ateammeeting forgreat testing.Automated atask andsaved hoursof manualeffort.Had a test failbecause oftimezone orlocalizationissues.Preparedsomethingfor QAonsite.Skipped techdebt days tofinish anurgent ticket.Wrote a testcase for acompletelyunrealisticscenario.Answeredto a requestin supportchannel.Had to clarifythat QAdoesn’t “ownqualityalone.”

QA - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
  1. Spent hours debugging only to find it was a typo.
  2. Rejected a developer's "It's not a bug; it's a feature" excuse.
  3. Conducted a knowledge sharing session.
  4. Disabled a test “temporarily” — 3 months ago.
  5. Found a bug in production.
  6. Used ChatGPT or Stack Overflow to fix a test failure.
  7. Ran the same test multiple times just to make sure.
  8. Watched a developer fix one bug and introduce two more.
  9. Wrote a flaky test.
  10. Used the phrase, "It works on my machine."
  11. Filed a bug, only to realize it was already in the backlog since last year.
  12. Ticket moved back and forth between QA and Dev a few times.
  13. Discovered an edge case no one thought of.
  14. Helped a developer reproduce a bug they couldn’t see.
  15. Improved the test process for the whole team.
  16. Discovered a performance issue during load testing.
  17. Got a shoutout in a team meeting for great testing.
  18. Automated a task and saved hours of manual effort.
  19. Had a test fail because of timezone or localization issues.
  20. Prepared something for QA onsite.
  21. Skipped tech debt days to finish an urgent ticket.
  22. Wrote a test case for a completely unrealistic scenario.
  23. Answered to a request in support channel.
  24. Had to clarify that QA doesn’t “own quality alone.”