Bugs foundpostdeploymentDetermineexpectationsof a productEarlytestingis bestIt workson mylocalFunctionaltestingAutomateeverything!EnhancedqualityVolumeTestingAutomationtestingCollaborationis keyUser flowandsatisfactionPesticideParadoxTightdealinesDevelopersshould testtheir owncodeBingoSoftwaretesting fallspart ofQualityAssuranceIncrementaltestingPerformancetestingRetestingLack oftestdataDefectclusteringExhaustivetestingSetting upthe testenvironmentBusiness-critical testscases shouldbeautomatedTestcase andscenarioNon-functionaltestingSoftwarebehavesasexpectedTestingprocessesshould beregularlyreviewedAbsenceof bugs isa fallacyBugs foundpostdeploymentDetermineexpectationsof a productEarlytestingis bestIt workson mylocalFunctionaltestingAutomateeverything!EnhancedqualityVolumeTestingAutomationtestingCollaborationis keyUser flowandsatisfactionPesticideParadoxTightdealinesDevelopersshould testtheir owncodeBingoSoftwaretesting fallspart ofQualityAssuranceIncrementaltestingPerformancetestingRetestingLack oftestdataDefectclusteringExhaustivetestingSetting upthe testenvironmentBusiness-critical testscases shouldbeautomatedTestcase andscenarioNon-functionaltestingSoftwarebehavesasexpectedTestingprocessesshould beregularlyreviewedAbsenceof bugs isa fallacy

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