IaC wasn'tapplied totestenvironmentsTestenvironmentwas missingcriticaldependenciesToo manydependencies,making testsunreliableSecuritypolicies weren'tenforced innon-prodenvironmentsAccidentallydeployed tothe wrongenvironmentTest data wasoutdated ormissing,causing falsetest resultsHad to waittoo long fora testenvironmentShared testenvironmentscausedconflictsbetween teamsToo manyflaky testsdue tounstable testenvironmentsHad to requesttestenvironmentaccess insteadof self-serviceEnvironmentworkedyesterday,but is brokentodayTestenvironmentgot wipedunexpectedlyCouldn't runtests due toresourcelimitationsSpent hoursdebugging, onlyto realize it wasa versionmismatchEnvironmentwent down inthe middle oftestingHad tomanuallyconfigure testenvironmentsNomonitoringtool in testenvironmentsStaging andproductionwere notidenticalForgot to cleanup a testenvironment,leading tounexpectedcostsNo visibilityinto what'srunningwhereCouldn'treproduce aproduction bugbecause testenvironmentwas differentImproperlysecured secretsor credentials intestenvironmentWorks indev, failsin prodRollbackfailed due toinconsistentenvironmentsIaC wasn'tapplied totestenvironmentsTestenvironmentwas missingcriticaldependenciesToo manydependencies,making testsunreliableSecuritypolicies weren'tenforced innon-prodenvironmentsAccidentallydeployed tothe wrongenvironmentTest data wasoutdated ormissing,causing falsetest resultsHad to waittoo long fora testenvironmentShared testenvironmentscausedconflictsbetween teamsToo manyflaky testsdue tounstable testenvironmentsHad to requesttestenvironmentaccess insteadof self-serviceEnvironmentworkedyesterday,but is brokentodayTestenvironmentgot wipedunexpectedlyCouldn't runtests due toresourcelimitationsSpent hoursdebugging, onlyto realize it wasa versionmismatchEnvironmentwent down inthe middle oftestingHad tomanuallyconfigure testenvironmentsNomonitoringtool in testenvironmentsStaging andproductionwere notidenticalForgot to cleanup a testenvironment,leading tounexpectedcostsNo visibilityinto what'srunningwhereCouldn'treproduce aproduction bugbecause testenvironmentwas differentImproperlysecured secretsor credentials intestenvironmentWorks indev, failsin prodRollbackfailed 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. IaC wasn't applied to test environments
  2. Test environment was missing critical dependencies
  3. Too many dependencies, making tests unreliable
  4. Security policies weren't enforced in non-prod environments
  5. Accidentally deployed to the wrong environment
  6. Test data was outdated or missing, causing false test results
  7. Had to wait too long for a test environment
  8. Shared test environments caused conflicts between teams
  9. Too many flaky tests due to unstable test environments
  10. Had to request test environment access instead of self-service
  11. Environment worked yesterday, but is broken today
  12. Test environment got wiped unexpectedly
  13. Couldn't run tests due to resource limitations
  14. Spent hours debugging, only to realize it was a version mismatch
  15. Environment went down in the middle of testing
  16. Had to manually configure test environments
  17. No monitoring tool in test environments
  18. Staging and production were not identical
  19. Forgot to clean up a test environment, leading to unexpected costs
  20. No visibility into what's running where
  21. Couldn't reproduce a production bug because test environment was different
  22. Improperly secured secrets or credentials in test environment
  23. Works in dev, fails in prod
  24. Rollback failed due to inconsistent environments