Testingprocessesshould beregularlyreviewedBusiness-critical testscases shouldbeautomatedExhaustivetestingPesticideParadoxAutomationtestingIt workson mylocalRetestingNon-functionaltestingAutomateeverything!DefectclusteringTestcase andscenarioPerformancetestingUser flowandsatisfactionLack oftestdataDevelopersshould testtheir owncodeSetting upthe testenvironmentFunctionaltestingSoftwaretesting fallspart ofQualityAssuranceAbsenceof bugs isa fallacyDetermineexpectationsof a productTightdealinesVolumeTestingCollaborationis keySoftwarebehavesasexpectedEarlytestingis bestEnhancedqualityBugs foundpostdeploymentBingoIncrementaltestingTestingprocessesshould beregularlyreviewedBusiness-critical testscases shouldbeautomatedExhaustivetestingPesticideParadoxAutomationtestingIt workson mylocalRetestingNon-functionaltestingAutomateeverything!DefectclusteringTestcase andscenarioPerformancetestingUser flowandsatisfactionLack oftestdataDevelopersshould testtheir owncodeSetting upthe testenvironmentFunctionaltestingSoftwaretesting fallspart ofQualityAssuranceAbsenceof bugs isa fallacyDetermineexpectationsof a productTightdealinesVolumeTestingCollaborationis keySoftwarebehavesasexpectedEarlytestingis bestEnhancedqualityBugs foundpostdeploymentBingoIncrementaltesting

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