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