TightdealinesBusiness-critical testscases shouldbeautomatedFunctionaltestingExhaustivetestingSetting upthe testenvironmentIncrementaltestingRetestingAutomationtestingIt workson mylocalAbsenceof bugs isa fallacyEnhancedqualityDevelopersshould testtheir owncodeUser flowandsatisfactionSoftwarebehavesasexpectedTestcase andscenarioNon-functionaltestingBingoPesticideParadoxSoftwaretesting fallspart ofQualityAssuranceDetermineexpectationsof a productLack oftestdataPerformancetestingBugs foundpostdeploymentVolumeTestingAutomateeverything!DefectclusteringEarlytestingis bestCollaborationis keyTestingprocessesshould beregularlyreviewedTightdealinesBusiness-critical testscases shouldbeautomatedFunctionaltestingExhaustivetestingSetting upthe testenvironmentIncrementaltestingRetestingAutomationtestingIt workson mylocalAbsenceof bugs isa fallacyEnhancedqualityDevelopersshould testtheir owncodeUser flowandsatisfactionSoftwarebehavesasexpectedTestcase andscenarioNon-functionaltestingBingoPesticideParadoxSoftwaretesting fallspart ofQualityAssuranceDetermineexpectationsof a productLack oftestdataPerformancetestingBugs foundpostdeploymentVolumeTestingAutomateeverything!DefectclusteringEarlytestingis bestCollaborationis keyTestingprocessesshould beregularlyreviewed

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