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