VolumeTestingSoftwarebehavesasexpectedCollaborationis keyRetestingTightdealinesTestingprocessesshould beregularlyreviewedNon-functionaltestingDetermineexpectationsof a productPerformancetestingBingoSetting upthe testenvironmentLack oftestdataUser flowandsatisfactionAutomateeverything!Business-critical testscases shouldbeautomatedPesticideParadoxFunctionaltestingEarlytestingis bestAbsenceof bugs isa fallacyBugs foundpostdeploymentDevelopersshould testtheir owncodeExhaustivetestingDefectclusteringIncrementaltestingAutomationtestingTestcase andscenarioIt workson mylocalEnhancedqualitySoftwaretesting fallspart ofQualityAssuranceVolumeTestingSoftwarebehavesasexpectedCollaborationis keyRetestingTightdealinesTestingprocessesshould beregularlyreviewedNon-functionaltestingDetermineexpectationsof a productPerformancetestingBingoSetting upthe testenvironmentLack oftestdataUser flowandsatisfactionAutomateeverything!Business-critical testscases shouldbeautomatedPesticideParadoxFunctionaltestingEarlytestingis bestAbsenceof bugs isa fallacyBugs foundpostdeploymentDevelopersshould testtheir owncodeExhaustivetestingDefectclusteringIncrementaltestingAutomationtestingTestcase andscenarioIt workson mylocalEnhancedqualitySoftwaretesting fallspart ofQualityAssurance

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