Developersshould testtheir owncodeCollaborationis keyRetestingVolumeTestingSoftwaretesting fallspart ofQualityAssuranceAutomationtestingDetermineexpectationsof a productSoftwarebehavesasexpectedAutomateeverything!IncrementaltestingBingoPesticideParadoxTightdealinesTestcase andscenarioEnhancedqualityIt workson mylocalSetting upthe testenvironmentTestingprocessesshould beregularlyreviewedAbsenceof bugs isa fallacyPerformancetestingLack oftestdataExhaustivetestingUser flowandsatisfactionDefectclusteringEarlytestingis bestBugs foundpostdeploymentBusiness-critical testscases shouldbeautomatedNon-functionaltestingFunctionaltestingDevelopersshould testtheir owncodeCollaborationis keyRetestingVolumeTestingSoftwaretesting fallspart ofQualityAssuranceAutomationtestingDetermineexpectationsof a productSoftwarebehavesasexpectedAutomateeverything!IncrementaltestingBingoPesticideParadoxTightdealinesTestcase andscenarioEnhancedqualityIt workson mylocalSetting upthe testenvironmentTestingprocessesshould beregularlyreviewedAbsenceof bugs isa fallacyPerformancetestingLack oftestdataExhaustivetestingUser flowandsatisfactionDefectclusteringEarlytestingis bestBugs foundpostdeploymentBusiness-critical testscases shouldbeautomatedNon-functionaltestingFunctionaltesting

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