BingoRetestingVolumeTestingCollaborationis keyTightdealinesNon-functionaltestingPerformancetestingEarlytestingis bestDevelopersshould testtheir owncodeTestcase andscenarioDetermineexpectationsof a productAutomateeverything!PesticideParadoxFunctionaltestingTestingprocessesshould beregularlyreviewedBugs foundpostdeploymentAbsenceof bugs isa fallacySetting upthe testenvironmentLack oftestdataDefectclusteringSoftwarebehavesasexpectedSoftwaretesting fallspart ofQualityAssuranceUser flowandsatisfactionExhaustivetestingBusiness-critical testscases shouldbeautomatedEnhancedqualityIt workson mylocalIncrementaltestingAutomationtestingBingoRetestingVolumeTestingCollaborationis keyTightdealinesNon-functionaltestingPerformancetestingEarlytestingis bestDevelopersshould testtheir owncodeTestcase andscenarioDetermineexpectationsof a productAutomateeverything!PesticideParadoxFunctionaltestingTestingprocessesshould beregularlyreviewedBugs foundpostdeploymentAbsenceof bugs isa fallacySetting upthe testenvironmentLack oftestdataDefectclusteringSoftwarebehavesasexpectedSoftwaretesting fallspart ofQualityAssuranceUser flowandsatisfactionExhaustivetestingBusiness-critical testscases shouldbeautomatedEnhancedqualityIt workson mylocalIncrementaltestingAutomationtesting

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