IncrementaltestingTestingprocessesshould beregularlyreviewedNon-functionaltestingCollaborationis keyAutomateeverything!TightdealinesIt workson mylocalAutomationtestingEarlytestingis bestEnhancedqualityUser flowandsatisfactionDevelopersshould testtheir owncodeSoftwarebehavesasexpectedTestcase andscenarioLack oftestdataBugs foundpostdeploymentRetestingVolumeTestingDefectclusteringBingoPerformancetestingExhaustivetestingSoftwaretesting fallspart ofQualityAssuranceFunctionaltestingDetermineexpectationsof a productSetting upthe testenvironmentPesticideParadoxAbsenceof bugs isa fallacyBusiness-critical testscases shouldbeautomatedIncrementaltestingTestingprocessesshould beregularlyreviewedNon-functionaltestingCollaborationis keyAutomateeverything!TightdealinesIt workson mylocalAutomationtestingEarlytestingis bestEnhancedqualityUser flowandsatisfactionDevelopersshould testtheir owncodeSoftwarebehavesasexpectedTestcase andscenarioLack oftestdataBugs foundpostdeploymentRetestingVolumeTestingDefectclusteringBingoPerformancetestingExhaustivetestingSoftwaretesting fallspart ofQualityAssuranceFunctionaltestingDetermineexpectationsof a productSetting upthe testenvironmentPesticideParadoxAbsenceof bugs isa fallacyBusiness-critical testscases shouldbeautomated

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