Determineexpectationsof a productIt workson mylocalPerformancetestingSoftwarebehavesasexpectedBingoFunctionaltestingBugs foundpostdeploymentRetestingTestcase andscenarioVolumeTestingBusiness-critical testscases shouldbeautomatedAutomateeverything!ExhaustivetestingTightdealinesIncrementaltestingTestingprocessesshould beregularlyreviewedAutomationtestingPesticideParadoxLack oftestdataUser flowandsatisfactionEarlytestingis bestSetting upthe testenvironmentNon-functionaltestingCollaborationis keyAbsenceof bugs isa fallacyDevelopersshould testtheir owncodeSoftwaretesting fallspart ofQualityAssuranceEnhancedqualityDefectclusteringDetermineexpectationsof a productIt workson mylocalPerformancetestingSoftwarebehavesasexpectedBingoFunctionaltestingBugs foundpostdeploymentRetestingTestcase andscenarioVolumeTestingBusiness-critical testscases shouldbeautomatedAutomateeverything!ExhaustivetestingTightdealinesIncrementaltestingTestingprocessesshould beregularlyreviewedAutomationtestingPesticideParadoxLack oftestdataUser flowandsatisfactionEarlytestingis bestSetting upthe testenvironmentNon-functionaltestingCollaborationis keyAbsenceof bugs isa fallacyDevelopersshould testtheir owncodeSoftwaretesting fallspart ofQualityAssuranceEnhancedqualityDefectclustering

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