Business-critical testscases shouldbeautomatedPerformancetestingEnhancedqualityTestcase andscenarioBingoNon-functionaltestingAbsenceof bugs isa fallacyRetestingPesticideParadoxVolumeTestingIncrementaltestingEarlytestingis bestFunctionaltestingSoftwarebehavesasexpectedExhaustivetestingDevelopersshould testtheir owncodeLack oftestdataBugs foundpostdeploymentTightdealinesAutomateeverything!DefectclusteringDetermineexpectationsof a productCollaborationis keyIt workson mylocalUser flowandsatisfactionAutomationtestingSoftwaretesting fallspart ofQualityAssuranceSetting upthe testenvironmentTestingprocessesshould beregularlyreviewedBusiness-critical testscases shouldbeautomatedPerformancetestingEnhancedqualityTestcase andscenarioBingoNon-functionaltestingAbsenceof bugs isa fallacyRetestingPesticideParadoxVolumeTestingIncrementaltestingEarlytestingis bestFunctionaltestingSoftwarebehavesasexpectedExhaustivetestingDevelopersshould testtheir owncodeLack oftestdataBugs foundpostdeploymentTightdealinesAutomateeverything!DefectclusteringDetermineexpectationsof a productCollaborationis keyIt workson mylocalUser flowandsatisfactionAutomationtestingSoftwaretesting fallspart ofQualityAssuranceSetting upthe testenvironmentTestingprocessesshould beregularlyreviewed

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