Test data wasoutdated ormissing,causing falsetest resultsHad tomanuallyconfigure testenvironmentsHad to waittoo long fora testenvironmentNomonitoringtool in testenvironmentsShared testenvironmentscausedconflictsbetween teamsWorks indev, failsin prodStaging andproductionwere notidenticalSecuritypolicies weren'tenforced innon-prodenvironmentsCouldn'treproduce aproduction bugbecause testenvironmentwas differentEnvironmentwent down inthe middle oftestingCouldn't runtests due toresourcelimitationsNo visibilityinto what'srunningwhereHad to requesttestenvironmentaccess insteadof self-serviceIaC wasn'tapplied totestenvironmentsToo manyflaky testsdue tounstable testenvironmentsRollbackfailed due toinconsistentenvironmentsEnvironmentworkedyesterday,but is brokentodayTestenvironmentwas missingcriticaldependenciesForgot to cleanup a testenvironment,leading tounexpectedcostsSpent hoursdebugging, onlyto realize it wasa versionmismatchAccidentallydeployed tothe wrongenvironmentTestenvironmentgot wipedunexpectedlyToo manydependencies,making testsunreliableImproperlysecured secretsor credentials intestenvironmentTest data wasoutdated ormissing,causing falsetest resultsHad tomanuallyconfigure testenvironmentsHad to waittoo long fora testenvironmentNomonitoringtool in testenvironmentsShared testenvironmentscausedconflictsbetween teamsWorks indev, failsin prodStaging andproductionwere notidenticalSecuritypolicies weren'tenforced innon-prodenvironmentsCouldn'treproduce aproduction bugbecause testenvironmentwas differentEnvironmentwent down inthe middle oftestingCouldn't runtests due toresourcelimitationsNo visibilityinto what'srunningwhereHad to requesttestenvironmentaccess insteadof self-serviceIaC wasn'tapplied totestenvironmentsToo manyflaky testsdue tounstable testenvironmentsRollbackfailed due toinconsistentenvironmentsEnvironmentworkedyesterday,but is brokentodayTestenvironmentwas missingcriticaldependenciesForgot to cleanup a testenvironment,leading tounexpectedcostsSpent hoursdebugging, onlyto realize it wasa versionmismatchAccidentallydeployed tothe wrongenvironmentTestenvironmentgot wipedunexpectedlyToo manydependencies,making testsunreliableImproperlysecured secretsor credentials intestenvironment

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