Accidentallydeployed tothe wrongenvironmentEnvironmentwent down inthe middle oftestingNomonitoringtool in testenvironmentsCouldn'treproduce aproduction bugbecause testenvironmentwas differentToo manyflaky testsdue tounstable testenvironmentsWorks indev, failsin prodSpent hoursdebugging, onlyto realize it wasa versionmismatchImproperlysecured secretsor credentials intestenvironmentHad to waittoo long fora testenvironmentSecuritypolicies weren'tenforced innon-prodenvironmentsNo visibilityinto what'srunningwhereCouldn't runtests due toresourcelimitationsForgot to cleanup a testenvironment,leading tounexpectedcostsRollbackfailed due toinconsistentenvironmentsShared testenvironmentscausedconflictsbetween teamsTest data wasoutdated ormissing,causing falsetest resultsHad to requesttestenvironmentaccess insteadof self-serviceIaC wasn'tapplied totestenvironmentsEnvironmentworkedyesterday,but is brokentodayTestenvironmentgot wipedunexpectedlyTestenvironmentwas missingcriticaldependenciesHad tomanuallyconfigure testenvironmentsStaging andproductionwere notidenticalToo manydependencies,making testsunreliableAccidentallydeployed tothe wrongenvironmentEnvironmentwent down inthe middle oftestingNomonitoringtool in testenvironmentsCouldn'treproduce aproduction bugbecause testenvironmentwas differentToo manyflaky testsdue tounstable testenvironmentsWorks indev, failsin prodSpent hoursdebugging, onlyto realize it wasa versionmismatchImproperlysecured secretsor credentials intestenvironmentHad to waittoo long fora testenvironmentSecuritypolicies weren'tenforced innon-prodenvironmentsNo visibilityinto what'srunningwhereCouldn't runtests due toresourcelimitationsForgot to cleanup a testenvironment,leading tounexpectedcostsRollbackfailed due toinconsistentenvironmentsShared testenvironmentscausedconflictsbetween teamsTest data wasoutdated ormissing,causing falsetest resultsHad to requesttestenvironmentaccess insteadof self-serviceIaC wasn'tapplied totestenvironmentsEnvironmentworkedyesterday,but is brokentodayTestenvironmentgot wipedunexpectedlyTestenvironmentwas missingcriticaldependenciesHad tomanuallyconfigure testenvironmentsStaging andproductionwere notidenticalToo manydependencies,making testsunreliable

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