Djangomigrationfails"URL Tabdoesn'tclose onstop"Sanitycheck?(usererror)"Manualtimedoesn'twork"Pottershenaniganswaste awhole dayRickHamiltonfinds abug"This MRneeds tobe release,not master"FixingTestLinkspellingerrorsRubin'sVMexplodesShawnwall oftext MRRubyCrash"Michael, I'massigningyou theSAML test""Did youclear yourcache?"Therelease islate (wecare)Longdebateabout devcycleSupport/salesengineergives RC tocustomer"We canalwaysmake a sub-release"Therelease islate (wedon't care)Dev pusheschanges towrongbranch"Did youcheck thelogs?"DanDaltonfinds abugLast minute"emergency"issueDjangomigrationfails"URL Tabdoesn'tclose onstop"Sanitycheck?(usererror)"Manualtimedoesn'twork"Pottershenaniganswaste awhole dayRickHamiltonfinds abug"This MRneeds tobe release,not master"FixingTestLinkspellingerrorsRubin'sVMexplodesShawnwall oftext MRRubyCrash"Michael, I'massigningyou theSAML test""Did youclear yourcache?"Therelease islate (wecare)Longdebateabout devcycleSupport/salesengineergives RC tocustomer"We canalwaysmake a sub-release"Therelease islate (wedon't care)Dev pusheschanges towrongbranch"Did youcheck thelogs?"DanDaltonfinds abugLast minute"emergency"issue

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