It workson mylocalVolumeTestingDevelopersshould testtheir owncodeCollaborationis keyEnhancedqualityBugs foundpostdeploymentBusiness-critical testscases shouldbeautomatedTestcase andscenarioPerformancetestingFunctionaltestingTestingprocessesshould beregularlyreviewedRetestingSetting upthe testenvironmentNon-functionaltestingUser flowandsatisfactionEarlytestingis bestSoftwarebehavesasexpectedIncrementaltestingPesticideParadoxTightdealinesSoftwaretesting fallspart ofQualityAssuranceDefectclusteringDetermineexpectationsof a productLack oftestdataExhaustivetestingAbsenceof bugs isa fallacyBingoAutomateeverything!AutomationtestingIt workson mylocalVolumeTestingDevelopersshould testtheir owncodeCollaborationis keyEnhancedqualityBugs foundpostdeploymentBusiness-critical testscases shouldbeautomatedTestcase andscenarioPerformancetestingFunctionaltestingTestingprocessesshould beregularlyreviewedRetestingSetting upthe testenvironmentNon-functionaltestingUser flowandsatisfactionEarlytestingis bestSoftwarebehavesasexpectedIncrementaltestingPesticideParadoxTightdealinesSoftwaretesting fallspart ofQualityAssuranceDefectclusteringDetermineexpectationsof a productLack oftestdataExhaustivetestingAbsenceof bugs isa fallacyBingoAutomateeverything!Automationtesting

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