It workson mylocalAbsenceof bugs isa fallacyPesticideParadoxAutomateeverything!AutomationtestingExhaustivetestingSoftwarebehavesasexpectedBusiness-critical testscases shouldbeautomatedNon-functionaltestingSoftwaretesting fallspart ofQualityAssuranceBingoSetting upthe testenvironmentTestingprocessesshould beregularlyreviewedFunctionaltestingVolumeTestingLack oftestdataEnhancedqualityTestcase andscenarioEarlytestingis bestTightdealinesUser flowandsatisfactionDetermineexpectationsof a productBugs foundpostdeploymentRetestingPerformancetestingIncrementaltestingDefectclusteringDevelopersshould testtheir owncodeCollaborationis keyIt workson mylocalAbsenceof bugs isa fallacyPesticideParadoxAutomateeverything!AutomationtestingExhaustivetestingSoftwarebehavesasexpectedBusiness-critical testscases shouldbeautomatedNon-functionaltestingSoftwaretesting fallspart ofQualityAssuranceBingoSetting upthe testenvironmentTestingprocessesshould beregularlyreviewedFunctionaltestingVolumeTestingLack oftestdataEnhancedqualityTestcase andscenarioEarlytestingis bestTightdealinesUser flowandsatisfactionDetermineexpectationsof a productBugs foundpostdeploymentRetestingPerformancetestingIncrementaltestingDefectclusteringDevelopersshould testtheir owncodeCollaborationis key

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