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

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