Environmentworkedyesterday,but is brokentodayToo manydependencies,making testsunreliableTestenvironmentwas missingcriticaldependenciesStaging andproductionwere notidenticalAccidentallydeployed tothe wrongenvironmentEnvironmentwent down inthe middle oftestingToo manyflaky testsdue tounstable testenvironmentsNomonitoringtool in testenvironmentsHad to requesttestenvironmentaccess insteadof self-serviceForgot to cleanup a testenvironment,leading tounexpectedcostsTestenvironmentgot wipedunexpectedlyImproperlysecured secretsor credentials intestenvironmentSpent hoursdebugging, onlyto realize it wasa versionmismatchShared testenvironmentscausedconflictsbetween teamsHad to waittoo long fora testenvironmentWorks indev, failsin prodTest data wasoutdated ormissing,causing falsetest resultsCouldn't runtests due toresourcelimitationsHad tomanuallyconfigure testenvironmentsCouldn'treproduce aproduction bugbecause testenvironmentwas differentSecuritypolicies weren'tenforced innon-prodenvironmentsIaC wasn'tapplied totestenvironmentsNo visibilityinto what'srunningwhereRollbackfailed due toinconsistentenvironmentsEnvironmentworkedyesterday,but is brokentodayToo manydependencies,making testsunreliableTestenvironmentwas missingcriticaldependenciesStaging andproductionwere notidenticalAccidentallydeployed tothe wrongenvironmentEnvironmentwent down inthe middle oftestingToo manyflaky testsdue tounstable testenvironmentsNomonitoringtool in testenvironmentsHad to requesttestenvironmentaccess insteadof self-serviceForgot to cleanup a testenvironment,leading tounexpectedcostsTestenvironmentgot wipedunexpectedlyImproperlysecured secretsor credentials intestenvironmentSpent hoursdebugging, onlyto realize it wasa versionmismatchShared testenvironmentscausedconflictsbetween teamsHad to waittoo long fora testenvironmentWorks indev, failsin prodTest data wasoutdated ormissing,causing falsetest resultsCouldn't runtests due toresourcelimitationsHad tomanuallyconfigure testenvironmentsCouldn'treproduce aproduction bugbecause testenvironmentwas differentSecuritypolicies weren'tenforced innon-prodenvironmentsIaC wasn'tapplied totestenvironmentsNo visibilityinto what'srunningwhereRollbackfailed due toinconsistentenvironments

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