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

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