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