Setting upthe testenvironmentIncrementaltestingLack oftestdataDevelopersshould testtheir owncodeBugs foundpostdeploymentAbsenceof bugs isa fallacyEnhancedqualityNon-functionaltestingTestcase andscenarioUser flowandsatisfactionSoftwarebehavesasexpectedVolumeTestingRetestingSoftwaretesting fallspart ofQualityAssuranceExhaustivetestingDefectclusteringPerformancetestingBusiness-critical testscases shouldbeautomatedCollaborationis keyTightdealinesDetermineexpectationsof a productPesticideParadoxAutomateeverything!Earlytestingis bestTestingprocessesshould beregularlyreviewedAutomationtestingIt workson mylocalBingoFunctionaltestingSetting upthe testenvironmentIncrementaltestingLack oftestdataDevelopersshould testtheir owncodeBugs foundpostdeploymentAbsenceof bugs isa fallacyEnhancedqualityNon-functionaltestingTestcase andscenarioUser flowandsatisfactionSoftwarebehavesasexpectedVolumeTestingRetestingSoftwaretesting fallspart ofQualityAssuranceExhaustivetestingDefectclusteringPerformancetestingBusiness-critical testscases shouldbeautomatedCollaborationis keyTightdealinesDetermineexpectationsof a productPesticideParadoxAutomateeverything!Earlytestingis bestTestingprocessesshould beregularlyreviewedAutomationtestingIt workson mylocalBingoFunctionaltesting

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