This bingo card has a free space and 24 words: Discovered a performance issue during load testing., Got a shoutout in a team meeting for great testing., Found a bug in production., Filed a bug, only to realize it was already in the backlog since last year., Rejected a developer's "It's not a bug; it's a feature" excuse., Skipped tech debt days to finish an urgent ticket., Had a test fail because of timezone or localization issues., Ticket moved back and forth between QA and Dev a few times., Watched a developer fix one bug and introduce two more., Disabled a test “temporarily” — 3 months ago., Used the phrase, "It works on my machine.", Conducted a knowledge sharing session., Helped a developer reproduce a bug they couldn’t see., Improved the test process for the whole team., Used ChatGPT or Stack Overflow to fix a test failure., Ran the same test multiple times just to make sure., Prepared something for QA onsite., Answered to a request in support channel., Wrote a test case for a completely unrealistic scenario., Discovered an edge case no one thought of., Spent hours debugging only to find it was a typo., Wrote a flaky test., Automated a task and saved hours of manual effort. and Had to clarify that QA doesn’t “own quality alone.”.
Bug Bash | Ascenda QA | ISTQB Study Group: Get To Know Game | Cadence Bingo | QA Team Bingo
Share this URL with your players:
For more control of your online game, create a clone of this card first.
Learn how to conduct a bingo game.
With players vying for a you'll have to call about __ items before someone wins. There's a __% chance that a lucky player would win after calling __ items.
Tip: If you want your game to last longer (on average), add more unique words/images to it.
