Accidentallydeployed tothe wrongenvironmentWorks indev, failsin prodCouldn'treproduce aproduction bugbecause testenvironmentwas differentCouldn't runtests due toresourcelimitationsTestenvironmentgot wipedunexpectedlyShared testenvironmentscausedconflictsbetween teamsTestenvironmentwas missingcriticaldependenciesToo manydependencies,making testsunreliableEnvironmentworkedyesterday,but is brokentodayForgot to cleanup a testenvironment,leading tounexpectedcostsEnvironmentwent down inthe middle oftestingHad to requesttestenvironmentaccess insteadof self-serviceSecuritypolicies weren'tenforced innon-prodenvironmentsNomonitoringtool in testenvironmentsHad to waittoo long fora testenvironmentNo visibilityinto what'srunningwhereIaC wasn'tapplied totestenvironmentsSpent hoursdebugging, onlyto realize it wasa versionmismatchRollbackfailed due toinconsistentenvironmentsHad tomanuallyconfigure testenvironmentsTest data wasoutdated ormissing,causing falsetest resultsToo manyflaky testsdue tounstable testenvironmentsStaging andproductionwere notidenticalImproperlysecured secretsor credentials intestenvironmentAccidentallydeployed tothe wrongenvironmentWorks indev, failsin prodCouldn'treproduce aproduction bugbecause testenvironmentwas differentCouldn't runtests due toresourcelimitationsTestenvironmentgot wipedunexpectedlyShared testenvironmentscausedconflictsbetween teamsTestenvironmentwas missingcriticaldependenciesToo manydependencies,making testsunreliableEnvironmentworkedyesterday,but is brokentodayForgot to cleanup a testenvironment,leading tounexpectedcostsEnvironmentwent down inthe middle oftestingHad to requesttestenvironmentaccess insteadof self-serviceSecuritypolicies weren'tenforced innon-prodenvironmentsNomonitoringtool in testenvironmentsHad to waittoo long fora testenvironmentNo visibilityinto what'srunningwhereIaC wasn'tapplied totestenvironmentsSpent hoursdebugging, onlyto realize it wasa versionmismatchRollbackfailed due toinconsistentenvironmentsHad tomanuallyconfigure testenvironmentsTest data wasoutdated ormissing,causing falsetest resultsToo manyflaky testsdue tounstable testenvironmentsStaging andproductionwere notidenticalImproperlysecured secretsor credentials intestenvironment

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