IncrementaltestingDetermineexpectationsof a productVolumeTestingLack oftestdataSetting upthe testenvironmentPesticideParadoxPerformancetestingSoftwaretesting fallspart ofQualityAssuranceAutomationtestingEnhancedqualityRetestingFunctionaltestingCollaborationis keyTestcase andscenarioSoftwarebehavesasexpectedIt workson mylocalBugs foundpostdeploymentUser flowandsatisfactionAutomateeverything!Business-critical testscases shouldbeautomatedTightdealinesAbsenceof bugs isa fallacyDevelopersshould testtheir owncodeDefectclusteringNon-functionaltestingTestingprocessesshould beregularlyreviewedExhaustivetestingBingoEarlytestingis bestIncrementaltestingDetermineexpectationsof a productVolumeTestingLack oftestdataSetting upthe testenvironmentPesticideParadoxPerformancetestingSoftwaretesting fallspart ofQualityAssuranceAutomationtestingEnhancedqualityRetestingFunctionaltestingCollaborationis keyTestcase andscenarioSoftwarebehavesasexpectedIt workson mylocalBugs foundpostdeploymentUser flowandsatisfactionAutomateeverything!Business-critical testscases shouldbeautomatedTightdealinesAbsenceof bugs isa fallacyDevelopersshould testtheir owncodeDefectclusteringNon-functionaltestingTestingprocessesshould beregularlyreviewedExhaustivetestingBingoEarlytestingis best

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