No visibilityinto what'srunningwhereTestenvironmentgot wipedunexpectedlyNomonitoringtool in testenvironmentsTestenvironmentwas missingcriticaldependenciesStaging andproductionwere notidenticalShared testenvironmentscausedconflictsbetween teamsAccidentallydeployed tothe wrongenvironmentEnvironmentworkedyesterday,but is brokentodayWorks indev, failsin prodHad tomanuallyconfigure testenvironmentsEnvironmentwent down inthe middle oftestingCouldn't runtests due toresourcelimitationsRollbackfailed due toinconsistentenvironmentsToo manydependencies,making testsunreliableCouldn'treproduce aproduction bugbecause testenvironmentwas differentSpent hoursdebugging, onlyto realize it wasa versionmismatchToo manyflaky testsdue tounstable testenvironmentsHad to waittoo long fora testenvironmentSecuritypolicies weren'tenforced innon-prodenvironmentsForgot to cleanup a testenvironment,leading tounexpectedcostsHad to requesttestenvironmentaccess insteadof self-serviceTest data wasoutdated ormissing,causing falsetest resultsImproperlysecured secretsor credentials intestenvironmentIaC wasn'tapplied totestenvironmentsNo visibilityinto what'srunningwhereTestenvironmentgot wipedunexpectedlyNomonitoringtool in testenvironmentsTestenvironmentwas missingcriticaldependenciesStaging andproductionwere notidenticalShared testenvironmentscausedconflictsbetween teamsAccidentallydeployed tothe wrongenvironmentEnvironmentworkedyesterday,but is brokentodayWorks indev, failsin prodHad tomanuallyconfigure testenvironmentsEnvironmentwent down inthe middle oftestingCouldn't runtests due toresourcelimitationsRollbackfailed due toinconsistentenvironmentsToo manydependencies,making testsunreliableCouldn'treproduce aproduction bugbecause testenvironmentwas differentSpent hoursdebugging, onlyto realize it wasa versionmismatchToo manyflaky testsdue tounstable testenvironmentsHad to waittoo long fora testenvironmentSecuritypolicies weren'tenforced innon-prodenvironmentsForgot to cleanup a testenvironment,leading tounexpectedcostsHad to requesttestenvironmentaccess insteadof self-serviceTest data wasoutdated ormissing,causing falsetest resultsImproperlysecured secretsor credentials intestenvironmentIaC 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. No visibility into what's running where
  2. Test environment got wiped unexpectedly
  3. No monitoring tool in test environments
  4. Test environment was missing critical dependencies
  5. Staging and production were not identical
  6. Shared test environments caused conflicts between teams
  7. Accidentally deployed to the wrong environment
  8. Environment worked yesterday, but is broken today
  9. Works in dev, fails in prod
  10. Had to manually configure test environments
  11. Environment went down in the middle of testing
  12. Couldn't run tests due to resource limitations
  13. Rollback failed due to inconsistent environments
  14. Too many dependencies, making tests unreliable
  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. Too many flaky tests due to unstable test environments
  18. Had to wait too long for a test environment
  19. Security policies weren't enforced in non-prod environments
  20. Forgot to clean up a test environment, leading to unexpected costs
  21. Had to request test environment access instead of self-service
  22. Test data was outdated or missing, causing false test results
  23. Improperly secured secrets or credentials in test environment
  24. IaC wasn't applied to test environments