AutomationtestingBingoFunctionaltestingAbsenceof bugs isa fallacyIt workson mylocalSetting upthe testenvironmentCollaborationis keyDefectclusteringTestcase andscenarioPerformancetestingEnhancedqualityTightdealinesTestingprocessesshould beregularlyreviewedSoftwarebehavesasexpectedBusiness-critical testscases shouldbeautomatedSoftwaretesting fallspart ofQualityAssuranceExhaustivetestingIncrementaltestingDetermineexpectationsof a productUser flowandsatisfactionNon-functionaltestingLack oftestdataAutomateeverything!VolumeTestingDevelopersshould testtheir owncodeRetestingEarlytestingis bestPesticideParadoxBugs foundpostdeploymentAutomationtestingBingoFunctionaltestingAbsenceof bugs isa fallacyIt workson mylocalSetting upthe testenvironmentCollaborationis keyDefectclusteringTestcase andscenarioPerformancetestingEnhancedqualityTightdealinesTestingprocessesshould beregularlyreviewedSoftwarebehavesasexpectedBusiness-critical testscases shouldbeautomatedSoftwaretesting fallspart ofQualityAssuranceExhaustivetestingIncrementaltestingDetermineexpectationsof a productUser flowandsatisfactionNon-functionaltestingLack oftestdataAutomateeverything!VolumeTestingDevelopersshould testtheir owncodeRetestingEarlytestingis bestPesticideParadoxBugs foundpostdeployment

Software Testing - Call List

(Print) Use this randomly generated list as your call list when playing the game. 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
O
2
G
3
B
4
G
5
O
6
I
7
B
8
G
9
N
10
O
11
G
12
N
13
N
14
B
15
N
16
B
17
I
18
B
19
B
20
O
21
O
22
I
23
O
24
I
25
G
26
G
27
I
28
I
29
N
  1. O-Automation testing
  2. G-Bingo
  3. B-Functional testing
  4. G-Absence of bugs is a fallacy
  5. O-It works on my local
  6. I-Setting up the test environment
  7. B-Collaboration is key
  8. G-Defect clustering
  9. N-Test case and scenario
  10. O-Performance testing
  11. G-Enhanced quality
  12. N-Tight dealines
  13. N-Testing processes should be regularly reviewed
  14. B-Software behaves as expected
  15. N-Business-critical tests cases should be automated
  16. B-Software testing falls part of Quality Assurance
  17. I-Exhaustive testing
  18. B-Incremental testing
  19. B-Determine expectations of a product
  20. O-User flow and satisfaction
  21. O-Non-functional testing
  22. I-Lack of test data
  23. O-Automate everything!
  24. I-Volume Testing
  25. G-Developers should test their own code
  26. G-Retesting
  27. I-Early testing is best
  28. I-Pesticide Paradox
  29. N-Bugs found post deployment