IncrementaltestingExhaustivetestingFunctionaltestingSoftwaretesting fallspart ofQualityAssuranceEnhancedqualityTestingprocessesshould beregularlyreviewedCollaborationis keyPesticideParadoxIt workson mylocalBingoBugs foundpostdeploymentLack oftestdataDetermineexpectationsof a productSetting upthe testenvironmentDevelopersshould testtheir owncodeBusiness-critical testscases shouldbeautomatedNon-functionaltestingAbsenceof bugs isa fallacyAutomateeverything!Testcase andscenarioTightdealinesUser flowandsatisfactionDefectclusteringAutomationtestingSoftwarebehavesasexpectedPerformancetestingEarlytestingis bestVolumeTestingRetestingIncrementaltestingExhaustivetestingFunctionaltestingSoftwaretesting fallspart ofQualityAssuranceEnhancedqualityTestingprocessesshould beregularlyreviewedCollaborationis keyPesticideParadoxIt workson mylocalBingoBugs foundpostdeploymentLack oftestdataDetermineexpectationsof a productSetting upthe testenvironmentDevelopersshould testtheir owncodeBusiness-critical testscases shouldbeautomatedNon-functionaltestingAbsenceof bugs isa fallacyAutomateeverything!Testcase andscenarioTightdealinesUser flowandsatisfactionDefectclusteringAutomationtestingSoftwarebehavesasexpectedPerformancetestingEarlytestingis bestVolumeTestingRetesting

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