Testcase andscenarioBugs foundpostdeploymentSoftwaretesting fallspart ofQualityAssuranceSetting upthe testenvironmentIt workson mylocalLack oftestdataSoftwarebehavesasexpectedIncrementaltestingEarlytestingis bestBusiness-critical testscases shouldbeautomatedTestingprocessesshould beregularlyreviewedExhaustivetestingVolumeTestingTightdealinesCollaborationis keyRetestingNon-functionaltestingEnhancedqualityPesticideParadoxBingoAutomateeverything!DefectclusteringFunctionaltestingDetermineexpectationsof a productAbsenceof bugs isa fallacyPerformancetestingAutomationtestingDevelopersshould testtheir owncodeUser flowandsatisfactionTestcase andscenarioBugs foundpostdeploymentSoftwaretesting fallspart ofQualityAssuranceSetting upthe testenvironmentIt workson mylocalLack oftestdataSoftwarebehavesasexpectedIncrementaltestingEarlytestingis bestBusiness-critical testscases shouldbeautomatedTestingprocessesshould beregularlyreviewedExhaustivetestingVolumeTestingTightdealinesCollaborationis keyRetestingNon-functionaltestingEnhancedqualityPesticideParadoxBingoAutomateeverything!DefectclusteringFunctionaltestingDetermineexpectationsof a productAbsenceof bugs isa fallacyPerformancetestingAutomationtestingDevelopersshould testtheir owncodeUser flowandsatisfaction

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