FixingTestLinkspellingerrors"Did youcheck thelogs?""Did youclear yourcache?"DanDaltonfinds abug"Michael, I'massigningyou theSAML test"RickHamiltonfinds abugShawnwall oftext MRDev pusheschanges towrongbranchTherelease islate (wedon't care)Pottershenaniganswaste awhole daySupport/salesengineergives RC tocustomerSanitycheck?(usererror)"URL Tabdoesn'tclose onstop""Manualtimedoesn'twork"Therelease islate (wecare)"This MRneeds tobe release,not master"Longdebateabout devcycleRubin'sVMexplodesLast minute"emergency"issueDjangomigrationfailsRubyCrash"We canalwaysmake a sub-release"FixingTestLinkspellingerrors"Did youcheck thelogs?""Did youclear yourcache?"DanDaltonfinds abug"Michael, I'massigningyou theSAML test"RickHamiltonfinds abugShawnwall oftext MRDev pusheschanges towrongbranchTherelease islate (wedon't care)Pottershenaniganswaste awhole daySupport/salesengineergives RC tocustomerSanitycheck?(usererror)"URL Tabdoesn'tclose onstop""Manualtimedoesn'twork"Therelease islate (wecare)"This MRneeds tobe release,not master"Longdebateabout devcycleRubin'sVMexplodesLast minute"emergency"issueDjangomigrationfailsRubyCrash"We canalwaysmake a sub-release"

RC Testing - 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. Fixing TestLink spelling errors
  2. "Did you check the logs?"
  4. "Did you clear your cache?"
  5. Dan Dalton finds a bug
  6. "Michael, I'm assigning you the SAML test"
  7. Rick Hamilton finds a bug
  8. Shawn wall of text MR
  9. Dev pushes changes to wrong branch
  10. The release is late (we don't care)
  11. Potter shenanigans waste a whole day
  12. Support/sales engineer gives RC to customer
  14. Sanity check? (user error)
  15. "URL Tab doesn't close on stop"
  16. "Manual time doesn't work"
  17. The release is late (we care)
  18. "This MR needs to be release, not master"
  19. Long debate about dev cycle
  20. Rubin's VM explodes
  21. Last minute "emergency" issue
  22. Django migration fails
  23. Ruby Crash
  24. "We can always make a sub-release"