Setting upthe testenvironmentFunctionaltestingIt workson mylocalSoftwaretesting fallspart ofQualityAssuranceBugs foundpostdeploymentDefectclusteringTestingprocessesshould beregularlyreviewedTestcase andscenarioExhaustivetestingDetermineexpectationsof a productBusiness-critical testscases shouldbeautomatedDevelopersshould testtheir owncodeIncrementaltestingNon-functionaltestingRetestingTightdealinesPerformancetestingUser flowandsatisfactionLack oftestdataAbsenceof bugs isa fallacyAutomateeverything!AutomationtestingEarlytestingis bestPesticideParadoxEnhancedqualityVolumeTestingCollaborationis keyBingoSoftwarebehavesasexpectedSetting upthe testenvironmentFunctionaltestingIt workson mylocalSoftwaretesting fallspart ofQualityAssuranceBugs foundpostdeploymentDefectclusteringTestingprocessesshould beregularlyreviewedTestcase andscenarioExhaustivetestingDetermineexpectationsof a productBusiness-critical testscases shouldbeautomatedDevelopersshould testtheir owncodeIncrementaltestingNon-functionaltestingRetestingTightdealinesPerformancetestingUser flowandsatisfactionLack oftestdataAbsenceof bugs isa fallacyAutomateeverything!AutomationtestingEarlytestingis bestPesticideParadoxEnhancedqualityVolumeTestingCollaborationis keyBingoSoftwarebehavesasexpected

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