Bugs foundpostdeploymentPesticideParadoxUser flowandsatisfactionBingoEarlytestingis bestSoftwaretesting fallspart ofQualityAssuranceAutomationtestingEnhancedqualityDevelopersshould testtheir owncodeTestcase andscenarioAutomateeverything!Non-functionaltestingSetting upthe testenvironmentDefectclusteringVolumeTestingTestingprocessesshould beregularlyreviewedDetermineexpectationsof a productSoftwarebehavesasexpectedIncrementaltestingCollaborationis keyPerformancetestingIt workson mylocalLack oftestdataBusiness-critical testscases shouldbeautomatedTightdealinesFunctionaltestingRetestingExhaustivetestingAbsenceof bugs isa fallacyBugs foundpostdeploymentPesticideParadoxUser flowandsatisfactionBingoEarlytestingis bestSoftwaretesting fallspart ofQualityAssuranceAutomationtestingEnhancedqualityDevelopersshould testtheir owncodeTestcase andscenarioAutomateeverything!Non-functionaltestingSetting upthe testenvironmentDefectclusteringVolumeTestingTestingprocessesshould beregularlyreviewedDetermineexpectationsof a productSoftwarebehavesasexpectedIncrementaltestingCollaborationis keyPerformancetestingIt workson mylocalLack oftestdataBusiness-critical testscases shouldbeautomatedTightdealinesFunctionaltestingRetestingExhaustivetestingAbsenceof bugs isa fallacy

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