Accidentallydeployed tothe wrongenvironmentNomonitoringtool in testenvironmentsTestenvironmentwas missingcriticaldependenciesIaC wasn'tapplied totestenvironmentsToo manyflaky testsdue tounstable testenvironmentsToo manydependencies,making testsunreliableTestenvironmentgot wipedunexpectedlyStaging andproductionwere notidenticalShared testenvironmentscausedconflictsbetween teamsTest data wasoutdated ormissing,causing falsetest resultsSecuritypolicies weren'tenforced innon-prodenvironmentsForgot to cleanup a testenvironment,leading tounexpectedcostsImproperlysecured secretsor credentials intestenvironmentNo visibilityinto what'srunningwhereCouldn'treproduce aproduction bugbecause testenvironmentwas differentSpent hoursdebugging, onlyto realize it wasa versionmismatchHad to requesttestenvironmentaccess insteadof self-serviceHad to waittoo long fora testenvironmentEnvironmentworkedyesterday,but is brokentodayRollbackfailed due toinconsistentenvironmentsEnvironmentwent down inthe middle oftestingCouldn't runtests due toresourcelimitationsWorks indev, failsin prodHad tomanuallyconfigure testenvironmentsAccidentallydeployed tothe wrongenvironmentNomonitoringtool in testenvironmentsTestenvironmentwas missingcriticaldependenciesIaC wasn'tapplied totestenvironmentsToo manyflaky testsdue tounstable testenvironmentsToo manydependencies,making testsunreliableTestenvironmentgot wipedunexpectedlyStaging andproductionwere notidenticalShared testenvironmentscausedconflictsbetween teamsTest data wasoutdated ormissing,causing falsetest resultsSecuritypolicies weren'tenforced innon-prodenvironmentsForgot to cleanup a testenvironment,leading tounexpectedcostsImproperlysecured secretsor credentials intestenvironmentNo visibilityinto what'srunningwhereCouldn'treproduce aproduction bugbecause testenvironmentwas differentSpent hoursdebugging, onlyto realize it wasa versionmismatchHad to requesttestenvironmentaccess insteadof self-serviceHad to waittoo long fora testenvironmentEnvironmentworkedyesterday,but is brokentodayRollbackfailed due toinconsistentenvironmentsEnvironmentwent down inthe middle oftestingCouldn't runtests due toresourcelimitationsWorks indev, failsin prodHad tomanuallyconfigure testenvironments

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