Securitypolicies weren'tenforced innon-prodenvironmentsCouldn't runtests due toresourcelimitationsNo visibilityinto what'srunningwhereHad to requesttestenvironmentaccess insteadof self-serviceWorks indev, failsin prodStaging andproductionwere notidenticalToo manyflaky testsdue tounstable testenvironmentsRollbackfailed due toinconsistentenvironmentsEnvironmentwent down inthe middle oftestingToo manydependencies,making testsunreliableHad to waittoo long fora testenvironmentAccidentallydeployed tothe wrongenvironmentImproperlysecured secretsor credentials intestenvironmentNomonitoringtool in testenvironmentsIaC wasn'tapplied totestenvironmentsEnvironmentworkedyesterday,but is brokentodayForgot to cleanup a testenvironment,leading tounexpectedcostsTestenvironmentwas missingcriticaldependenciesCouldn'treproduce aproduction bugbecause testenvironmentwas differentShared testenvironmentscausedconflictsbetween teamsTest data wasoutdated ormissing,causing falsetest resultsTestenvironmentgot wipedunexpectedlyHad tomanuallyconfigure testenvironmentsSpent hoursdebugging, onlyto realize it wasa versionmismatchSecuritypolicies weren'tenforced innon-prodenvironmentsCouldn't runtests due toresourcelimitationsNo visibilityinto what'srunningwhereHad to requesttestenvironmentaccess insteadof self-serviceWorks indev, failsin prodStaging andproductionwere notidenticalToo manyflaky testsdue tounstable testenvironmentsRollbackfailed due toinconsistentenvironmentsEnvironmentwent down inthe middle oftestingToo manydependencies,making testsunreliableHad to waittoo long fora testenvironmentAccidentallydeployed tothe wrongenvironmentImproperlysecured secretsor credentials intestenvironmentNomonitoringtool in testenvironmentsIaC wasn'tapplied totestenvironmentsEnvironmentworkedyesterday,but is brokentodayForgot to cleanup a testenvironment,leading tounexpectedcostsTestenvironmentwas missingcriticaldependenciesCouldn'treproduce aproduction bugbecause testenvironmentwas differentShared testenvironmentscausedconflictsbetween teamsTest data wasoutdated ormissing,causing falsetest resultsTestenvironmentgot wipedunexpectedlyHad tomanuallyconfigure testenvironmentsSpent hoursdebugging, onlyto realize it wasa versionmismatch

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