Absenceof bugs isa fallacyAutomationtestingDevelopersshould testtheir owncodeIncrementaltestingSoftwaretesting fallspart ofQualityAssuranceEnhancedqualityTightdealinesSetting upthe testenvironmentDetermineexpectationsof a productDefectclusteringBusiness-critical testscases shouldbeautomatedAutomateeverything!Testcase andscenarioFunctionaltestingUser flowandsatisfactionRetestingPerformancetestingExhaustivetestingEarlytestingis bestPesticideParadoxTestingprocessesshould beregularlyreviewedCollaborationis keySoftwarebehavesasexpectedBugs foundpostdeploymentIt workson mylocalLack oftestdataVolumeTestingBingoNon-functionaltestingAbsenceof bugs isa fallacyAutomationtestingDevelopersshould testtheir owncodeIncrementaltestingSoftwaretesting fallspart ofQualityAssuranceEnhancedqualityTightdealinesSetting upthe testenvironmentDetermineexpectationsof a productDefectclusteringBusiness-critical testscases shouldbeautomatedAutomateeverything!Testcase andscenarioFunctionaltestingUser flowandsatisfactionRetestingPerformancetestingExhaustivetestingEarlytestingis bestPesticideParadoxTestingprocessesshould beregularlyreviewedCollaborationis keySoftwarebehavesasexpectedBugs foundpostdeploymentIt workson mylocalLack oftestdataVolumeTestingBingoNon-functionaltesting

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