Too manyflaky testsdue tounstable testenvironmentsCouldn'treproduce aproduction bugbecause testenvironmentwas differentHad tomanuallyconfigure testenvironmentsTestenvironmentgot wipedunexpectedlyForgot to cleanup a testenvironment,leading tounexpectedcostsWorks indev, failsin prodImproperlysecured secretsor credentials intestenvironmentTest data wasoutdated ormissing,causing falsetest resultsRollbackfailed due toinconsistentenvironmentsNo visibilityinto what'srunningwhereEnvironmentworkedyesterday,but is brokentodayHad to requesttestenvironmentaccess insteadof self-serviceNomonitoringtool in testenvironmentsIaC wasn'tapplied totestenvironmentsSpent hoursdebugging, onlyto realize it wasa versionmismatchTestenvironmentwas missingcriticaldependenciesStaging andproductionwere notidenticalShared testenvironmentscausedconflictsbetween teamsAccidentallydeployed tothe wrongenvironmentSecuritypolicies weren'tenforced innon-prodenvironmentsHad to waittoo long fora testenvironmentToo manydependencies,making testsunreliableEnvironmentwent down inthe middle oftestingCouldn't runtests due toresourcelimitationsToo manyflaky testsdue tounstable testenvironmentsCouldn'treproduce aproduction bugbecause testenvironmentwas differentHad tomanuallyconfigure testenvironmentsTestenvironmentgot wipedunexpectedlyForgot to cleanup a testenvironment,leading tounexpectedcostsWorks indev, failsin prodImproperlysecured secretsor credentials intestenvironmentTest data wasoutdated ormissing,causing falsetest resultsRollbackfailed due toinconsistentenvironmentsNo visibilityinto what'srunningwhereEnvironmentworkedyesterday,but is brokentodayHad to requesttestenvironmentaccess insteadof self-serviceNomonitoringtool in testenvironmentsIaC wasn'tapplied totestenvironmentsSpent hoursdebugging, onlyto realize it wasa versionmismatchTestenvironmentwas missingcriticaldependenciesStaging andproductionwere notidenticalShared testenvironmentscausedconflictsbetween teamsAccidentallydeployed tothe wrongenvironmentSecuritypolicies weren'tenforced innon-prodenvironmentsHad to waittoo long fora testenvironmentToo manydependencies,making testsunreliableEnvironmentwent down inthe middle oftestingCouldn't runtests due toresourcelimitations

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