Setting upthe testenvironmentRetestingIncrementaltestingAutomationtestingDefectclusteringSoftwarebehavesasexpectedAbsenceof bugs isa fallacyBusiness-critical testscases shouldbeautomatedExhaustivetestingTightdealinesBugs foundpostdeploymentNon-functionaltestingFunctionaltestingSoftwaretesting fallspart ofQualityAssuranceEnhancedqualityEarlytestingis bestUser flowandsatisfactionTestcase andscenarioPesticideParadoxCollaborationis keyIt workson mylocalLack oftestdataTestingprocessesshould beregularlyreviewedDetermineexpectationsof a productDevelopersshould testtheir owncodeVolumeTestingAutomateeverything!PerformancetestingBingoSetting upthe testenvironmentRetestingIncrementaltestingAutomationtestingDefectclusteringSoftwarebehavesasexpectedAbsenceof bugs isa fallacyBusiness-critical testscases shouldbeautomatedExhaustivetestingTightdealinesBugs foundpostdeploymentNon-functionaltestingFunctionaltestingSoftwaretesting fallspart ofQualityAssuranceEnhancedqualityEarlytestingis bestUser flowandsatisfactionTestcase andscenarioPesticideParadoxCollaborationis keyIt workson mylocalLack oftestdataTestingprocessesshould beregularlyreviewedDetermineexpectationsof a productDevelopersshould testtheir owncodeVolumeTestingAutomateeverything!PerformancetestingBingo

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