Automateeverything!User flowandsatisfactionIncrementaltestingTestingprocessesshould beregularlyreviewedTightdealinesDefectclusteringSetting upthe testenvironmentVolumeTestingDetermineexpectationsof a productEnhancedqualityDevelopersshould testtheir owncodeIt workson mylocalFunctionaltestingSoftwarebehavesasexpectedNon-functionaltestingCollaborationis keyExhaustivetestingBugs foundpostdeploymentBusiness-critical testscases shouldbeautomatedAbsenceof bugs isa fallacyAutomationtestingLack oftestdataSoftwaretesting fallspart ofQualityAssuranceEarlytestingis bestTestcase andscenarioRetestingPesticideParadoxPerformancetestingBingoAutomateeverything!User flowandsatisfactionIncrementaltestingTestingprocessesshould beregularlyreviewedTightdealinesDefectclusteringSetting upthe testenvironmentVolumeTestingDetermineexpectationsof a productEnhancedqualityDevelopersshould testtheir owncodeIt workson mylocalFunctionaltestingSoftwarebehavesasexpectedNon-functionaltestingCollaborationis keyExhaustivetestingBugs foundpostdeploymentBusiness-critical testscases shouldbeautomatedAbsenceof bugs isa fallacyAutomationtestingLack oftestdataSoftwaretesting fallspart ofQualityAssuranceEarlytestingis bestTestcase andscenarioRetestingPesticideParadoxPerformancetestingBingo

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