Works indev, failsin prodRollbackfailed due toinconsistentenvironmentsToo manydependencies,making testsunreliableEnvironmentworkedyesterday,but is brokentodayCouldn't runtests due toresourcelimitationsStaging andproductionwere notidenticalTest data wasoutdated ormissing,causing falsetest resultsShared testenvironmentscausedconflictsbetween teamsAccidentallydeployed tothe wrongenvironmentHad to requesttestenvironmentaccess insteadof self-serviceTestenvironmentgot wipedunexpectedlySecuritypolicies weren'tenforced innon-prodenvironmentsCouldn'treproduce aproduction bugbecause testenvironmentwas differentHad tomanuallyconfigure testenvironmentsToo manyflaky testsdue tounstable testenvironmentsHad to waittoo long fora testenvironmentImproperlysecured secretsor credentials intestenvironmentEnvironmentwent down inthe middle oftestingIaC wasn'tapplied totestenvironmentsForgot to cleanup a testenvironment,leading tounexpectedcostsTestenvironmentwas missingcriticaldependenciesSpent hoursdebugging, onlyto realize it wasa versionmismatchNo visibilityinto what'srunningwhereNomonitoringtool in testenvironmentsWorks indev, failsin prodRollbackfailed due toinconsistentenvironmentsToo manydependencies,making testsunreliableEnvironmentworkedyesterday,but is brokentodayCouldn't runtests due toresourcelimitationsStaging andproductionwere notidenticalTest data wasoutdated ormissing,causing falsetest resultsShared testenvironmentscausedconflictsbetween teamsAccidentallydeployed tothe wrongenvironmentHad to requesttestenvironmentaccess insteadof self-serviceTestenvironmentgot wipedunexpectedlySecuritypolicies weren'tenforced innon-prodenvironmentsCouldn'treproduce aproduction bugbecause testenvironmentwas differentHad tomanuallyconfigure testenvironmentsToo manyflaky testsdue tounstable testenvironmentsHad to waittoo long fora testenvironmentImproperlysecured secretsor credentials intestenvironmentEnvironmentwent down inthe middle oftestingIaC wasn'tapplied totestenvironmentsForgot to cleanup a testenvironment,leading tounexpectedcostsTestenvironmentwas missingcriticaldependenciesSpent hoursdebugging, onlyto realize it wasa versionmismatchNo visibilityinto what'srunningwhereNomonitoringtool in 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. Works in dev, fails in prod
  2. Rollback failed due to inconsistent environments
  3. Too many dependencies, making tests unreliable
  4. Environment worked yesterday, but is broken today
  5. Couldn't run tests due to resource limitations
  6. Staging and production were not identical
  7. Test data was outdated or missing, causing false test results
  8. Shared test environments caused conflicts between teams
  9. Accidentally deployed to the wrong environment
  10. Had to request test environment access instead of self-service
  11. Test environment got wiped unexpectedly
  12. Security policies weren't enforced in non-prod environments
  13. Couldn't reproduce a production bug because test environment was different
  14. Had to manually configure test environments
  15. Too many flaky tests due to unstable test environments
  16. Had to wait too long for a test environment
  17. Improperly secured secrets or credentials in test environment
  18. Environment went down in the middle of testing
  19. IaC wasn't applied to test environments
  20. Forgot to clean up a test environment, leading to unexpected costs
  21. Test environment was missing critical dependencies
  22. Spent hours debugging, only to realize it was a version mismatch
  23. No visibility into what's running where
  24. No monitoring tool in test environments