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

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