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

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