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