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