Found abug inproduction.Discoveredan edgecase no onethought of.Automated atask andsaved hoursof manualeffort.Helped adeveloperreproduce abug theycouldn’t see.Answeredto a requestin supportchannel.Filed a bug,only to realizeit was alreadyin the backlogsince last year.Ran thesame testmultipletimes just tomake sure.Preparedsomethingfor QAonsite.Disabled atest“temporarily”— 3 monthsago.Discovered aperformanceissue duringload testing.Ticket movedback andforth betweenQA and Deva few times.Conducteda knowledgesharingsession.Watched adeveloper fixone bug andintroducetwo more.Wrote a testcase for acompletelyunrealisticscenario.Spent hoursdebuggingonly to find itwas a typo.Improved thetest processfor the wholeteam.Had a test failbecause oftimezone orlocalizationissues.Wrotea flakytest.Got ashoutout in ateammeeting forgreat testing.Used thephrase, "Itworks on mymachine."Skipped techdebt days tofinish anurgent ticket.UsedChatGPT orStackOverflow to fixa test failure.Rejected adeveloper's"It's not a bug;it's a feature"excuse.Had to clarifythat QAdoesn’t “ownqualityalone.”Found abug inproduction.Discoveredan edgecase no onethought of.Automated atask andsaved hoursof manualeffort.Helped adeveloperreproduce abug theycouldn’t see.Answeredto a requestin supportchannel.Filed a bug,only to realizeit was alreadyin the backlogsince last year.Ran thesame testmultipletimes just tomake sure.Preparedsomethingfor QAonsite.Disabled atest“temporarily”— 3 monthsago.Discovered aperformanceissue duringload testing.Ticket movedback andforth betweenQA and Deva few times.Conducteda knowledgesharingsession.Watched adeveloper fixone bug andintroducetwo more.Wrote a testcase for acompletelyunrealisticscenario.Spent hoursdebuggingonly to find itwas a typo.Improved thetest processfor the wholeteam.Had a test failbecause oftimezone orlocalizationissues.Wrotea flakytest.Got ashoutout in ateammeeting forgreat testing.Used thephrase, "Itworks on mymachine."Skipped techdebt days tofinish anurgent ticket.UsedChatGPT orStackOverflow to fixa test failure.Rejected adeveloper's"It's not a bug;it's a feature"excuse.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. Found a bug in production.
  2. Discovered an edge case no one thought of.
  3. Automated a task and saved hours of manual effort.
  4. Helped a developer reproduce a bug they couldn’t see.
  5. Answered to a request in support channel.
  6. Filed a bug, only to realize it was already in the backlog since last year.
  7. Ran the same test multiple times just to make sure.
  8. Prepared something for QA onsite.
  9. Disabled a test “temporarily” — 3 months ago.
  10. Discovered a performance issue during load testing.
  11. Ticket moved back and forth between QA and Dev a few times.
  12. Conducted a knowledge sharing session.
  13. Watched a developer fix one bug and introduce two more.
  14. Wrote a test case for a completely unrealistic scenario.
  15. Spent hours debugging only to find it was a typo.
  16. Improved the test process for the whole team.
  17. Had a test fail because of timezone or localization issues.
  18. Wrote a flaky test.
  19. Got a shoutout in a team meeting for great testing.
  20. Used the phrase, "It works on my machine."
  21. Skipped tech debt days to finish an urgent ticket.
  22. Used ChatGPT or Stack Overflow to fix a test failure.
  23. Rejected a developer's "It's not a bug; it's a feature" excuse.
  24. Had to clarify that QA doesn’t “own quality alone.”