Developersshould testtheir owncodeIt workson mylocalTestcase andscenarioPesticideParadoxEarlytestingis bestNon-functionaltestingEnhancedqualityDetermineexpectationsof a productSetting upthe testenvironmentAutomationtestingCollaborationis keyBusiness-critical testscases shouldbeautomatedBugs foundpostdeploymentRetestingExhaustivetestingVolumeTestingAutomateeverything!Softwaretesting fallspart ofQualityAssuranceFunctionaltestingIncrementaltestingDefectclusteringUser flowandsatisfactionTightdealinesLack oftestdataPerformancetestingSoftwarebehavesasexpectedBingoAbsenceof bugs isa fallacyTestingprocessesshould beregularlyreviewedDevelopersshould testtheir owncodeIt workson mylocalTestcase andscenarioPesticideParadoxEarlytestingis bestNon-functionaltestingEnhancedqualityDetermineexpectationsof a productSetting upthe testenvironmentAutomationtestingCollaborationis keyBusiness-critical testscases shouldbeautomatedBugs foundpostdeploymentRetestingExhaustivetestingVolumeTestingAutomateeverything!Softwaretesting fallspart ofQualityAssuranceFunctionaltestingIncrementaltestingDefectclusteringUser flowandsatisfactionTightdealinesLack oftestdataPerformancetestingSoftwarebehavesasexpectedBingoAbsenceof bugs isa fallacyTestingprocessesshould beregularlyreviewed

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