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

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