IaC wasn'tapplied totestenvironmentsCouldn't runtests due toresourcelimitationsEnvironmentwent down inthe middle oftestingAccidentallydeployed tothe wrongenvironmentImproperlysecured secretsor credentials intestenvironmentRollbackfailed due toinconsistentenvironmentsForgot to cleanup a testenvironment,leading tounexpectedcostsEnvironmentworkedyesterday,but is brokentodayToo manyflaky testsdue tounstable testenvironmentsToo manydependencies,making testsunreliableNo visibilityinto what'srunningwhereSpent hoursdebugging, onlyto realize it wasa versionmismatchHad to requesttestenvironmentaccess insteadof self-serviceCouldn'treproduce aproduction bugbecause testenvironmentwas differentTestenvironmentwas missingcriticaldependenciesTest data wasoutdated ormissing,causing falsetest resultsTestenvironmentgot wipedunexpectedlyShared testenvironmentscausedconflictsbetween teamsStaging andproductionwere notidenticalWorks indev, failsin prodNomonitoringtool in testenvironmentsSecuritypolicies weren'tenforced innon-prodenvironmentsHad to waittoo long fora testenvironmentHad tomanuallyconfigure testenvironmentsIaC wasn'tapplied totestenvironmentsCouldn't runtests due toresourcelimitationsEnvironmentwent down inthe middle oftestingAccidentallydeployed tothe wrongenvironmentImproperlysecured secretsor credentials intestenvironmentRollbackfailed due toinconsistentenvironmentsForgot to cleanup a testenvironment,leading tounexpectedcostsEnvironmentworkedyesterday,but is brokentodayToo manyflaky testsdue tounstable testenvironmentsToo manydependencies,making testsunreliableNo visibilityinto what'srunningwhereSpent hoursdebugging, onlyto realize it wasa versionmismatchHad to requesttestenvironmentaccess insteadof self-serviceCouldn'treproduce aproduction bugbecause testenvironmentwas differentTestenvironmentwas missingcriticaldependenciesTest data wasoutdated ormissing,causing falsetest resultsTestenvironmentgot wipedunexpectedlyShared testenvironmentscausedconflictsbetween teamsStaging andproductionwere notidenticalWorks indev, failsin prodNomonitoringtool in testenvironmentsSecuritypolicies weren'tenforced innon-prodenvironmentsHad to waittoo long fora testenvironmentHad tomanuallyconfigure testenvironments

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