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

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