AutomationtestingFunctionaltestingTestcase andscenarioSoftwaretesting fallspart ofQualityAssuranceUser flowandsatisfactionVolumeTestingSoftwarebehavesasexpectedExhaustivetestingRetestingDefectclusteringIt workson mylocalTestingprocessesshould beregularlyreviewedBusiness-critical testscases shouldbeautomatedEarlytestingis bestEnhancedqualityPerformancetestingCollaborationis keyDevelopersshould testtheir owncodeDetermineexpectationsof a productAbsenceof bugs isa fallacyIncrementaltestingBingoSetting upthe testenvironmentNon-functionaltestingPesticideParadoxBugs foundpostdeploymentTightdealinesLack oftestdataAutomateeverything!AutomationtestingFunctionaltestingTestcase andscenarioSoftwaretesting fallspart ofQualityAssuranceUser flowandsatisfactionVolumeTestingSoftwarebehavesasexpectedExhaustivetestingRetestingDefectclusteringIt workson mylocalTestingprocessesshould beregularlyreviewedBusiness-critical testscases shouldbeautomatedEarlytestingis bestEnhancedqualityPerformancetestingCollaborationis keyDevelopersshould testtheir owncodeDetermineexpectationsof a productAbsenceof bugs isa fallacyIncrementaltestingBingoSetting upthe testenvironmentNon-functionaltestingPesticideParadoxBugs foundpostdeploymentTightdealinesLack oftestdataAutomateeverything!

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