IaC wasn'tapplied totestenvironmentsImproperlysecured secretsor credentials intestenvironmentHad tomanuallyconfigure testenvironmentsTestenvironmentwas missingcriticaldependenciesAccidentallydeployed tothe wrongenvironmentToo manyflaky testsdue tounstable testenvironmentsEnvironmentwent down inthe middle oftestingSecuritypolicies weren'tenforced innon-prodenvironmentsTestenvironmentgot wipedunexpectedlyTest data wasoutdated ormissing,causing falsetest resultsStaging andproductionwere notidenticalNomonitoringtool in testenvironmentsNo visibilityinto what'srunningwhereRollbackfailed due toinconsistentenvironmentsHad to requesttestenvironmentaccess insteadof self-serviceEnvironmentworkedyesterday,but is brokentodayCouldn'treproduce aproduction bugbecause testenvironmentwas differentCouldn't runtests due toresourcelimitationsWorks indev, failsin prodShared testenvironmentscausedconflictsbetween teamsSpent hoursdebugging, onlyto realize it wasa versionmismatchToo manydependencies,making testsunreliableForgot to cleanup a testenvironment,leading tounexpectedcostsHad to waittoo long fora testenvironmentIaC wasn'tapplied totestenvironmentsImproperlysecured secretsor credentials intestenvironmentHad tomanuallyconfigure testenvironmentsTestenvironmentwas missingcriticaldependenciesAccidentallydeployed tothe wrongenvironmentToo manyflaky testsdue tounstable testenvironmentsEnvironmentwent down inthe middle oftestingSecuritypolicies weren'tenforced innon-prodenvironmentsTestenvironmentgot wipedunexpectedlyTest data wasoutdated ormissing,causing falsetest resultsStaging andproductionwere notidenticalNomonitoringtool in testenvironmentsNo visibilityinto what'srunningwhereRollbackfailed due toinconsistentenvironmentsHad to requesttestenvironmentaccess insteadof self-serviceEnvironmentworkedyesterday,but is brokentodayCouldn'treproduce aproduction bugbecause testenvironmentwas differentCouldn't runtests due toresourcelimitationsWorks indev, failsin prodShared testenvironmentscausedconflictsbetween teamsSpent hoursdebugging, onlyto realize it wasa versionmismatchToo manydependencies,making testsunreliableForgot to cleanup a testenvironment,leading tounexpectedcostsHad to waittoo long fora testenvironment

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