Collaborationis keyEarlytestingis bestNon-functionaltestingBusiness-critical testscases shouldbeautomatedSoftwaretesting fallspart ofQualityAssuranceIncrementaltestingSoftwarebehavesasexpectedAutomateeverything!AutomationtestingUser flowandsatisfactionDevelopersshould testtheir owncodeTightdealinesPerformancetestingIt workson mylocalBugs foundpostdeploymentPesticideParadoxEnhancedqualityRetestingSetting upthe testenvironmentLack oftestdataVolumeTestingAbsenceof bugs isa fallacyTestcase andscenarioDetermineexpectationsof a productTestingprocessesshould beregularlyreviewedDefectclusteringBingoFunctionaltestingExhaustivetestingCollaborationis keyEarlytestingis bestNon-functionaltestingBusiness-critical testscases shouldbeautomatedSoftwaretesting fallspart ofQualityAssuranceIncrementaltestingSoftwarebehavesasexpectedAutomateeverything!AutomationtestingUser flowandsatisfactionDevelopersshould testtheir owncodeTightdealinesPerformancetestingIt workson mylocalBugs foundpostdeploymentPesticideParadoxEnhancedqualityRetestingSetting upthe testenvironmentLack oftestdataVolumeTestingAbsenceof bugs isa fallacyTestcase andscenarioDetermineexpectationsof a productTestingprocessesshould beregularlyreviewedDefectclusteringBingoFunctionaltestingExhaustivetesting

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