PesticideParadoxSoftwarebehavesasexpectedTestingprocessesshould beregularlyreviewedDetermineexpectationsof a productAbsenceof bugs isa fallacyBingoEnhancedqualityLack oftestdataIt workson mylocalCollaborationis keyVolumeTestingAutomationtestingAutomateeverything!RetestingDefectclusteringSoftwaretesting fallspart ofQualityAssuranceBusiness-critical testscases shouldbeautomatedIncrementaltestingTestcase andscenarioSetting upthe testenvironmentTightdealinesUser flowandsatisfactionNon-functionaltestingBugs foundpostdeploymentExhaustivetestingEarlytestingis bestFunctionaltestingPerformancetestingDevelopersshould testtheir owncodePesticideParadoxSoftwarebehavesasexpectedTestingprocessesshould beregularlyreviewedDetermineexpectationsof a productAbsenceof bugs isa fallacyBingoEnhancedqualityLack oftestdataIt workson mylocalCollaborationis keyVolumeTestingAutomationtestingAutomateeverything!RetestingDefectclusteringSoftwaretesting fallspart ofQualityAssuranceBusiness-critical testscases shouldbeautomatedIncrementaltestingTestcase andscenarioSetting upthe testenvironmentTightdealinesUser flowandsatisfactionNon-functionaltestingBugs foundpostdeploymentExhaustivetestingEarlytestingis bestFunctionaltestingPerformancetestingDevelopersshould testtheir owncode

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