It workson mylocalLack oftestdataDetermineexpectationsof a productTightdealinesPesticideParadoxBugs foundpostdeploymentUser flowandsatisfactionBingoIncrementaltestingPerformancetestingDevelopersshould testtheir owncodeCollaborationis keyFunctionaltestingAutomationtestingSoftwarebehavesasexpectedVolumeTestingTestingprocessesshould beregularlyreviewedDefectclusteringSetting upthe testenvironmentBusiness-critical testscases shouldbeautomatedAbsenceof bugs isa fallacyExhaustivetestingSoftwaretesting fallspart ofQualityAssuranceNon-functionaltestingEarlytestingis bestRetestingEnhancedqualityTestcase andscenarioAutomateeverything!It workson mylocalLack oftestdataDetermineexpectationsof a productTightdealinesPesticideParadoxBugs foundpostdeploymentUser flowandsatisfactionBingoIncrementaltestingPerformancetestingDevelopersshould testtheir owncodeCollaborationis keyFunctionaltestingAutomationtestingSoftwarebehavesasexpectedVolumeTestingTestingprocessesshould beregularlyreviewedDefectclusteringSetting upthe testenvironmentBusiness-critical testscases shouldbeautomatedAbsenceof bugs isa fallacyExhaustivetestingSoftwaretesting fallspart ofQualityAssuranceNon-functionaltestingEarlytestingis bestRetestingEnhancedqualityTestcase andscenarioAutomateeverything!

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