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

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