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

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