Absenceof bugs isa fallacyEarlytestingis bestIt workson mylocalEnhancedqualityNon-functionaltestingLack oftestdataSoftwarebehavesasexpectedCollaborationis keyTestcase andscenarioAutomateeverything!FunctionaltestingTightdealinesVolumeTestingSoftwaretesting fallspart ofQualityAssuranceBusiness-critical testscases shouldbeautomatedPesticideParadoxBugs foundpostdeploymentRetestingTestingprocessesshould beregularlyreviewedAutomationtestingUser flowandsatisfactionSetting upthe testenvironmentDetermineexpectationsof a productExhaustivetestingPerformancetestingIncrementaltestingDefectclusteringDevelopersshould testtheir owncodeBingoAbsenceof bugs isa fallacyEarlytestingis bestIt workson mylocalEnhancedqualityNon-functionaltestingLack oftestdataSoftwarebehavesasexpectedCollaborationis keyTestcase andscenarioAutomateeverything!FunctionaltestingTightdealinesVolumeTestingSoftwaretesting fallspart ofQualityAssuranceBusiness-critical testscases shouldbeautomatedPesticideParadoxBugs foundpostdeploymentRetestingTestingprocessesshould beregularlyreviewedAutomationtestingUser flowandsatisfactionSetting upthe testenvironmentDetermineexpectationsof a productExhaustivetestingPerformancetestingIncrementaltestingDefectclusteringDevelopersshould testtheir owncodeBingo

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