IncrementaltestingAutomationtestingAutomateeverything!Developersshould testtheir owncodeBusiness-critical testscases shouldbeautomatedRetestingBugs foundpostdeploymentPesticideParadoxSoftwarebehavesasexpectedEarlytestingis bestDetermineexpectationsof a productTestcase andscenarioIt workson mylocalFunctionaltestingTightdealinesTestingprocessesshould beregularlyreviewedCollaborationis keyVolumeTestingExhaustivetestingSetting upthe testenvironmentNon-functionaltestingEnhancedqualityUser flowandsatisfactionAbsenceof bugs isa fallacyLack oftestdataPerformancetestingBingoSoftwaretesting fallspart ofQualityAssuranceDefectclusteringIncrementaltestingAutomationtestingAutomateeverything!Developersshould testtheir owncodeBusiness-critical testscases shouldbeautomatedRetestingBugs foundpostdeploymentPesticideParadoxSoftwarebehavesasexpectedEarlytestingis bestDetermineexpectationsof a productTestcase andscenarioIt workson mylocalFunctionaltestingTightdealinesTestingprocessesshould beregularlyreviewedCollaborationis keyVolumeTestingExhaustivetestingSetting upthe testenvironmentNon-functionaltestingEnhancedqualityUser flowandsatisfactionAbsenceof bugs isa fallacyLack oftestdataPerformancetestingBingoSoftwaretesting fallspart ofQualityAssuranceDefectclustering

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
O
3
O
4
G
5
N
6
G
7
N
8
I
9
B
10
I
11
B
12
N
13
O
14
B
15
N
16
N
17
B
18
I
19
I
20
I
21
O
22
G
23
O
24
G
25
I
26
O
27
G
28
B
29
G