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

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