It workson mylocalEnhancedqualitySoftwaretesting fallspart ofQualityAssuranceTightdealinesVolumeTestingSetting upthe testenvironmentCollaborationis keySoftwarebehavesasexpectedDefectclusteringUser flowandsatisfactionEarlytestingis bestRetestingNon-functionaltestingTestingprocessesshould beregularlyreviewedPerformancetestingFunctionaltestingPesticideParadoxAbsenceof bugs isa fallacyBusiness-critical testscases shouldbeautomatedExhaustivetestingBugs foundpostdeploymentBingoDetermineexpectationsof a productDevelopersshould testtheir owncodeTestcase andscenarioAutomationtestingIncrementaltestingLack oftestdataAutomateeverything!It workson mylocalEnhancedqualitySoftwaretesting fallspart ofQualityAssuranceTightdealinesVolumeTestingSetting upthe testenvironmentCollaborationis keySoftwarebehavesasexpectedDefectclusteringUser flowandsatisfactionEarlytestingis bestRetestingNon-functionaltestingTestingprocessesshould beregularlyreviewedPerformancetestingFunctionaltestingPesticideParadoxAbsenceof bugs isa fallacyBusiness-critical testscases shouldbeautomatedExhaustivetestingBugs foundpostdeploymentBingoDetermineexpectationsof a productDevelopersshould testtheir owncodeTestcase andscenarioAutomationtestingIncrementaltestingLack oftestdataAutomateeverything!

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