Rollbackfailed due toinconsistentenvironmentsEnvironmentwent down inthe middle oftestingHad to waittoo long fora testenvironmentSpent hoursdebugging, onlyto realize it wasa versionmismatchCouldn'treproduce aproduction bugbecause testenvironmentwas differentTestenvironmentwas missingcriticaldependenciesHad to requesttestenvironmentaccess insteadof self-serviceShared testenvironmentscausedconflictsbetween teamsTestenvironmentgot wipedunexpectedlyWorks indev, failsin prodEnvironmentworkedyesterday,but is brokentodayHad tomanuallyconfigure testenvironmentsToo manydependencies,making testsunreliableStaging andproductionwere notidenticalIaC wasn'tapplied totestenvironmentsNomonitoringtool in testenvironmentsImproperlysecured secretsor credentials intestenvironmentToo manyflaky testsdue tounstable testenvironmentsNo visibilityinto what'srunningwhereCouldn't runtests due toresourcelimitationsSecuritypolicies weren'tenforced innon-prodenvironmentsTest data wasoutdated ormissing,causing falsetest resultsAccidentallydeployed tothe wrongenvironmentForgot to cleanup a testenvironment,leading tounexpectedcostsRollbackfailed due toinconsistentenvironmentsEnvironmentwent down inthe middle oftestingHad to waittoo long fora testenvironmentSpent hoursdebugging, onlyto realize it wasa versionmismatchCouldn'treproduce aproduction bugbecause testenvironmentwas differentTestenvironmentwas missingcriticaldependenciesHad to requesttestenvironmentaccess insteadof self-serviceShared testenvironmentscausedconflictsbetween teamsTestenvironmentgot wipedunexpectedlyWorks indev, failsin prodEnvironmentworkedyesterday,but is brokentodayHad tomanuallyconfigure testenvironmentsToo manydependencies,making testsunreliableStaging andproductionwere notidenticalIaC wasn'tapplied totestenvironmentsNomonitoringtool in testenvironmentsImproperlysecured secretsor credentials intestenvironmentToo manyflaky testsdue tounstable testenvironmentsNo visibilityinto what'srunningwhereCouldn't runtests due toresourcelimitationsSecuritypolicies weren'tenforced innon-prodenvironmentsTest data wasoutdated ormissing,causing falsetest resultsAccidentallydeployed tothe wrongenvironmentForgot to cleanup a testenvironment,leading tounexpectedcosts

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