Accidentallydeployed tothe wrongenvironmentWorks indev, failsin prodEnvironmentwent down inthe middle oftestingStaging andproductionwere notidenticalNomonitoringtool in testenvironmentsSpent hoursdebugging, onlyto realize it wasa versionmismatchRollbackfailed due toinconsistentenvironmentsEnvironmentworkedyesterday,but is brokentodayNo visibilityinto what'srunningwhereHad tomanuallyconfigure testenvironmentsTestenvironmentwas missingcriticaldependenciesToo manyflaky testsdue tounstable testenvironmentsForgot to cleanup a testenvironment,leading tounexpectedcostsTestenvironmentgot wipedunexpectedlyHad to requesttestenvironmentaccess insteadof self-serviceTest data wasoutdated ormissing,causing falsetest resultsSecuritypolicies weren'tenforced innon-prodenvironmentsHad to waittoo long fora testenvironmentShared testenvironmentscausedconflictsbetween teamsImproperlysecured secretsor credentials intestenvironmentCouldn't runtests due toresourcelimitationsToo manydependencies,making testsunreliableCouldn'treproduce aproduction bugbecause testenvironmentwas differentIaC wasn'tapplied totestenvironmentsAccidentallydeployed tothe wrongenvironmentWorks indev, failsin prodEnvironmentwent down inthe middle oftestingStaging andproductionwere notidenticalNomonitoringtool in testenvironmentsSpent hoursdebugging, onlyto realize it wasa versionmismatchRollbackfailed due toinconsistentenvironmentsEnvironmentworkedyesterday,but is brokentodayNo visibilityinto what'srunningwhereHad tomanuallyconfigure testenvironmentsTestenvironmentwas missingcriticaldependenciesToo manyflaky testsdue tounstable testenvironmentsForgot to cleanup a testenvironment,leading tounexpectedcostsTestenvironmentgot wipedunexpectedlyHad to requesttestenvironmentaccess insteadof self-serviceTest data wasoutdated ormissing,causing falsetest resultsSecuritypolicies weren'tenforced innon-prodenvironmentsHad to waittoo long fora testenvironmentShared testenvironmentscausedconflictsbetween teamsImproperlysecured secretsor credentials intestenvironmentCouldn't runtests due toresourcelimitationsToo manydependencies,making testsunreliableCouldn'treproduce aproduction bugbecause testenvironmentwas differentIaC wasn'tapplied totestenvironments

TEM Bingo - 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. Accidentally deployed to the wrong environment
  2. Works in dev, fails in prod
  3. Environment went down in the middle of testing
  4. Staging and production were not identical
  5. No monitoring tool in test environments
  6. Spent hours debugging, only to realize it was a version mismatch
  7. Rollback failed due to inconsistent environments
  8. Environment worked yesterday, but is broken today
  9. No visibility into what's running where
  10. Had to manually configure test environments
  11. Test environment was missing critical dependencies
  12. Too many flaky tests due to unstable test environments
  13. Forgot to clean up a test environment, leading to unexpected costs
  14. Test environment got wiped unexpectedly
  15. Had to request test environment access instead of self-service
  16. Test data was outdated or missing, causing false test results
  17. Security policies weren't enforced in non-prod environments
  18. Had to wait too long for a test environment
  19. Shared test environments caused conflicts between teams
  20. Improperly secured secrets or credentials in test environment
  21. Couldn't run tests due to resource limitations
  22. Too many dependencies, making tests unreliable
  23. Couldn't reproduce a production bug because test environment was different
  24. IaC wasn't applied to test environments