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