TightdealinesBusiness-critical testscases shouldbeautomatedRetestingDefectclusteringSoftwarebehavesasexpectedTestcase andscenarioEnhancedqualityCollaborationis keyPerformancetestingBugs foundpostdeploymentDevelopersshould testtheir owncodeAbsenceof bugs isa fallacyAutomationtestingSoftwaretesting fallspart ofQualityAssuranceTestingprocessesshould beregularlyreviewedFunctionaltestingIncrementaltestingNon-functionaltestingLack oftestdataAutomateeverything!Earlytestingis bestUser flowandsatisfactionSetting upthe testenvironmentDetermineexpectationsof a productPesticideParadoxExhaustivetestingBingoIt workson mylocalVolumeTestingTightdealinesBusiness-critical testscases shouldbeautomatedRetestingDefectclusteringSoftwarebehavesasexpectedTestcase andscenarioEnhancedqualityCollaborationis keyPerformancetestingBugs foundpostdeploymentDevelopersshould testtheir owncodeAbsenceof bugs isa fallacyAutomationtestingSoftwaretesting fallspart ofQualityAssuranceTestingprocessesshould beregularlyreviewedFunctionaltestingIncrementaltestingNon-functionaltestingLack oftestdataAutomateeverything!Earlytestingis bestUser flowandsatisfactionSetting upthe testenvironmentDetermineexpectationsof a productPesticideParadoxExhaustivetestingBingoIt workson mylocalVolumeTesting

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