Environmentworkedyesterday,but is brokentodayToo manydependencies,making testsunreliableCouldn'treproduce aproduction bugbecause testenvironmentwas differentWorks indev, failsin prodStaging andproductionwere notidenticalShared testenvironmentscausedconflictsbetween teamsHad to waittoo long fora testenvironmentAccidentallydeployed tothe wrongenvironmentNomonitoringtool in testenvironmentsRollbackfailed due toinconsistentenvironmentsCouldn't runtests due toresourcelimitationsForgot to cleanup a testenvironment,leading tounexpectedcostsSpent hoursdebugging, onlyto realize it wasa versionmismatchTest data wasoutdated ormissing,causing falsetest resultsTestenvironmentwas missingcriticaldependenciesHad tomanuallyconfigure testenvironmentsHad to requesttestenvironmentaccess insteadof self-serviceEnvironmentwent down inthe middle oftestingIaC wasn'tapplied totestenvironmentsNo visibilityinto what'srunningwhereToo manyflaky testsdue tounstable testenvironmentsImproperlysecured secretsor credentials intestenvironmentTestenvironmentgot wipedunexpectedlySecuritypolicies weren'tenforced innon-prodenvironmentsEnvironmentworkedyesterday,but is brokentodayToo manydependencies,making testsunreliableCouldn'treproduce aproduction bugbecause testenvironmentwas differentWorks indev, failsin prodStaging andproductionwere notidenticalShared testenvironmentscausedconflictsbetween teamsHad to waittoo long fora testenvironmentAccidentallydeployed tothe wrongenvironmentNomonitoringtool in testenvironmentsRollbackfailed due toinconsistentenvironmentsCouldn't runtests due toresourcelimitationsForgot to cleanup a testenvironment,leading tounexpectedcostsSpent hoursdebugging, onlyto realize it wasa versionmismatchTest data wasoutdated ormissing,causing falsetest resultsTestenvironmentwas missingcriticaldependenciesHad tomanuallyconfigure testenvironmentsHad to requesttestenvironmentaccess insteadof self-serviceEnvironmentwent down inthe middle oftestingIaC wasn'tapplied totestenvironmentsNo visibilityinto what'srunningwhereToo manyflaky testsdue tounstable testenvironmentsImproperlysecured secretsor credentials intestenvironmentTestenvironmentgot wipedunexpectedlySecuritypolicies weren'tenforced innon-prodenvironments

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