Forgot to cleanup a testenvironment,leading tounexpectedcostsHad to waittoo long fora testenvironmentWorks indev, failsin prodStaging andproductionwere notidenticalCouldn'treproduce aproduction bugbecause testenvironmentwas differentAccidentallydeployed tothe wrongenvironmentTest data wasoutdated ormissing,causing falsetest resultsImproperlysecured secretsor credentials intestenvironmentIaC wasn'tapplied totestenvironmentsSpent hoursdebugging, onlyto realize it wasa versionmismatchToo manyflaky testsdue tounstable testenvironmentsTestenvironmentwas missingcriticaldependenciesSecuritypolicies weren'tenforced innon-prodenvironmentsToo manydependencies,making testsunreliableHad tomanuallyconfigure testenvironmentsEnvironmentwent down inthe middle oftestingTestenvironmentgot wipedunexpectedlyHad to requesttestenvironmentaccess insteadof self-serviceNomonitoringtool in testenvironmentsNo visibilityinto what'srunningwhereCouldn't runtests due toresourcelimitationsRollbackfailed due toinconsistentenvironmentsEnvironmentworkedyesterday,but is brokentodayShared testenvironmentscausedconflictsbetween teamsForgot to cleanup a testenvironment,leading tounexpectedcostsHad to waittoo long fora testenvironmentWorks indev, failsin prodStaging andproductionwere notidenticalCouldn'treproduce aproduction bugbecause testenvironmentwas differentAccidentallydeployed tothe wrongenvironmentTest data wasoutdated ormissing,causing falsetest resultsImproperlysecured secretsor credentials intestenvironmentIaC wasn'tapplied totestenvironmentsSpent hoursdebugging, onlyto realize it wasa versionmismatchToo manyflaky testsdue tounstable testenvironmentsTestenvironmentwas missingcriticaldependenciesSecuritypolicies weren'tenforced innon-prodenvironmentsToo manydependencies,making testsunreliableHad tomanuallyconfigure testenvironmentsEnvironmentwent down inthe middle oftestingTestenvironmentgot wipedunexpectedlyHad to requesttestenvironmentaccess insteadof self-serviceNomonitoringtool in testenvironmentsNo visibilityinto what'srunningwhereCouldn't runtests due toresourcelimitationsRollbackfailed due toinconsistentenvironmentsEnvironmentworkedyesterday,but is brokentodayShared testenvironmentscausedconflictsbetween teams

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