EnhancedqualitySetting upthe testenvironmentBingoSoftwarebehavesasexpectedDevelopersshould testtheir owncodeTestingprocessesshould beregularlyreviewedBugs foundpostdeploymentAutomateeverything!VolumeTestingTightdealinesIt workson mylocalFunctionaltestingAutomationtestingSoftwaretesting fallspart ofQualityAssurancePesticideParadoxPerformancetestingAbsenceof bugs isa fallacyDetermineexpectationsof a productDefectclusteringLack oftestdataCollaborationis keyIncrementaltestingBusiness-critical testscases shouldbeautomatedRetestingUser flowandsatisfactionTestcase andscenarioExhaustivetestingEarlytestingis bestNon-functionaltestingEnhancedqualitySetting upthe testenvironmentBingoSoftwarebehavesasexpectedDevelopersshould testtheir owncodeTestingprocessesshould beregularlyreviewedBugs foundpostdeploymentAutomateeverything!VolumeTestingTightdealinesIt workson mylocalFunctionaltestingAutomationtestingSoftwaretesting fallspart ofQualityAssurancePesticideParadoxPerformancetestingAbsenceof bugs isa fallacyDetermineexpectationsof a productDefectclusteringLack oftestdataCollaborationis keyIncrementaltestingBusiness-critical testscases shouldbeautomatedRetestingUser flowandsatisfactionTestcase andscenarioExhaustivetestingEarlytestingis bestNon-functionaltesting

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