Absenceof bugs isa fallacyBusiness-critical testscases shouldbeautomatedExhaustivetestingEnhancedqualityPesticideParadoxCollaborationis keyIt workson mylocalLack oftestdataDefectclusteringDevelopersshould testtheir owncodeTestcase andscenarioDetermineexpectationsof a productPerformancetestingAutomationtestingRetestingTestingprocessesshould beregularlyreviewedSetting upthe testenvironmentNon-functionaltestingTightdealinesVolumeTestingBugs foundpostdeploymentEarlytestingis bestIncrementaltestingSoftwaretesting fallspart ofQualityAssuranceFunctionaltestingUser flowandsatisfactionSoftwarebehavesasexpectedAutomateeverything!BingoAbsenceof bugs isa fallacyBusiness-critical testscases shouldbeautomatedExhaustivetestingEnhancedqualityPesticideParadoxCollaborationis keyIt workson mylocalLack oftestdataDefectclusteringDevelopersshould testtheir owncodeTestcase andscenarioDetermineexpectationsof a productPerformancetestingAutomationtestingRetestingTestingprocessesshould beregularlyreviewedSetting upthe testenvironmentNon-functionaltestingTightdealinesVolumeTestingBugs foundpostdeploymentEarlytestingis bestIncrementaltestingSoftwaretesting fallspart ofQualityAssuranceFunctionaltestingUser flowandsatisfactionSoftwarebehavesasexpectedAutomateeverything!Bingo

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