Determineexpectationsof a productBusiness-critical testscases shouldbeautomatedRetestingBingoVolumeTestingCollaborationis keyEarlytestingis bestDevelopersshould testtheir owncodeSoftwaretesting fallspart ofQualityAssuranceTestingprocessesshould beregularlyreviewedIncrementaltestingExhaustivetestingFunctionaltestingPesticideParadoxNon-functionaltestingBugs foundpostdeploymentAbsenceof bugs isa fallacyPerformancetestingLack oftestdataAutomateeverything!TightdealinesEnhancedqualityAutomationtestingSoftwarebehavesasexpectedSetting upthe testenvironmentIt workson mylocalUser flowandsatisfactionTestcase andscenarioDefectclusteringDetermineexpectationsof a productBusiness-critical testscases shouldbeautomatedRetestingBingoVolumeTestingCollaborationis keyEarlytestingis bestDevelopersshould testtheir owncodeSoftwaretesting fallspart ofQualityAssuranceTestingprocessesshould beregularlyreviewedIncrementaltestingExhaustivetestingFunctionaltestingPesticideParadoxNon-functionaltestingBugs foundpostdeploymentAbsenceof bugs isa fallacyPerformancetestingLack oftestdataAutomateeverything!TightdealinesEnhancedqualityAutomationtestingSoftwarebehavesasexpectedSetting upthe testenvironmentIt workson mylocalUser flowandsatisfactionTestcase andscenarioDefectclustering

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