Index_T

T

table construction example, combinatorial testing

Challenges parameter, 195 ‚ 196

cleanroom testing example, 248 ‚ 254

Coach Mode option, 196 ‚ 198

full combinatorial tables, 187

Game Speed options, 193 ‚ 194

Multiple Routes parameter, 198 ‚ 200

Play Calling values, 192

Quarter Length option, 191

as sanity tests, 209

taping techniques, ad hoc testing, 291

target audience section, concept documents, 89

tasks

art production planning, 93

task planning, pre-production test phase, 130 ‚ 134

TDD (technical design documents), 93, 417 ‚ 421

TE (Test Effectiveness), 175 ‚ 176

team summary section, concept documents, 90

teams

art team responsibilities

animators, 72 ‚ 74

art directors, 68 ‚ 70

artists , 71 ‚ 72

level designers, 74

development team responsibilities

build engineers , 65 ‚ 66

development engineers, 64 ‚ 65

development lead, 63 ‚ 64

game designer responsibilities, 79 ‚ 80

organization techniques, 81 ‚ 82

project manager responsibilities, 78 ‚ 79

sound team responsibilities

music directors/ producers , 77

sound engineers, 75 ‚ 77

team work advantages, automation testing, 331 ‚ 332

testing team responsibilities beta

testers, 67 ‚ 68

test engineers, 67

test leads, 66, 96

technical design documents (TDD), 93, 417 ‚ 421

Technical Requirements Checklist (TRC), 142

technical summary section, game design documents, 411

templates

combinatorial testing, 203 ‚ 205, 431 ‚ 434

quality factors, 123

TFDs (test flow diagrams)

craft item, 436

create/save, 437

heal character, 436

overview, 239 ‚ 240

powerups , 435

unlock, 437

Teraquest Web site, 119

terminators, test flow diagrams, 213

test cases

Allpairs tool example, 207

build cycles, 156 ‚ 158

creating from test paths, test flow diagrams, 236 ‚ 239

pre-production test phase, 137

test case trees, 269 ‚ 272

typographical errors, 158

Test Effectiveness (TE), 175 ‚ 176

test flow diagrams (TFDs)

actions, 212 ‚ 213

allocation activities, 214

in boxes, 219

construction activities, 214 ‚ 216

data dictionary

application use, 226

example of, 226 ‚ 229

overview, 225

reuse, 226

defect trigger examples, 321 ‚ 325

events, 212

example of, 220 ‚ 225

flow components , 211 ‚ 212

preparation activities, 214

primitives, 213

SmartDraw tool examples, 216 ‚ 218

states, 213

templates

craft item, 436

create/save, 437

heal character, 436

overview, 239 ‚ 240

powerups, 435

unlock, 437

terminators, 213

test paths

baseline path generation, 231 ‚ 233

expert path generation, 234 ‚ 235

minimum path generation, 231

overviews, 230

strategies, combining, 235 ‚ 236

test case creation from, 236 ‚ 239

usage inversion, cleanroom testing, 263 ‚ 266

when to use, 240

test paths

cleanroom testing, 254 ‚ 258

TFDs (test flow diagrams)

baseline path generation, 231 ‚ 233

expert path generation, 234 ‚ 235

minimum path generation, 231

overview, 230

strategies, combining, 235 ‚ 236

test case creation from, 236 ‚ 239

test plan documents, 421 ‚ 425

test steps, pre-production test phase, 137

test suite

build cycle, 156 ‚ 158

pre-production test phase, 137

test trees

test case trees, 269 ‚ 272

test tree designs, 275 ‚ 284

tree feature tests, 272 ‚ 274

testing

ad hoc

as detective testing, 293 ‚ 296

directed testing, 288, 293 ‚ 296

discussed, 158

free testing, 288, 292

fresh eyes concept, 288 ‚ 289

goal setting, 290

groupthink , avoiding, 292 ‚ 293

overview, 287

right-brain testing, 288

scientific method, 295 ‚ 296

taping techniques, 291

Alpha

Alpha entry criteria, 142 ‚ 143

overview, 141 ‚ 142

production cycles, 97 ‚ 98

automation tests

build management, 337

cost advantages, 327 ‚ 328

cost analysis, 339 ‚ 341

false expectations, 330

filtered results, 336

future of, 346 ‚ 348

infrastructure advantages, 331

load-testing, 344

MMP (massively multiplayer) games , 334 ‚ 335

regression, 344

reusability advantages, 328

scale matters, 329

The Sims Online example, 341 ‚ 343

team work advantages, 331 ‚ 332

when to use, 332 ‚ 333

Beta

Beta entry criteria, 144 ‚ 145

closed Beta testing, 99, 301

code freeze, 100

compliance testing, 98

crunch time, 98 ‚ 99

design lock, 145

external, 301 ‚ 302

feature lock, 145

open Beta testing, 99, 301

release guidelines, 147

waived defects, 146

black box, 151 ‚ 154

Blocked outcomes , 23

build cycles

configuration preparation, 160 ‚ 161

entry criteria, 158 ‚ 159

overview, 155

test cases, 156 ‚ 158

test suite, 156 ‚ 158

version control, 159

certification, 148 ‚ 149

character selection UI, 20 ‚ 21

cleanroom

Cleanroom Software Engineering, 243

combinatorial table example, 248 ‚ 254

flow usage, 258 ‚ 261

inverted usage, 261 ‚ 266

mode-based usage, 244

player type usage, 245 ‚ 246

real-life usage, 246 ‚ 247

test generation, 247

test paths, 254 ‚ 258

usage probabilities, 243 ‚ 244

combinatorial

Allpairs tool, 205 ‚ 209

boundaries, 186 ‚ 187

defaults, 184

defect trigger examples, 316 ‚ 320

dimensions, 190

enumerations, 185

heterogeneous tests, 184

homogenous tests, 184

inverted usage, cleanroom testing, 262 ‚ 263

pairwise tables, 188 ‚ 202

parameters, 183 ‚ 184

ranges, 185 ‚ 186

table templates, 431 ‚ 434

template use, 203 ‚ 205

values, 184

compliance, production cycles, 98

controller button presses, 22

Fails outcome, 23

game playing as, 20 ‚ 23

gold

GMCs (gold master candidates), 147

last-minute defects, 148

release candidates, 147

showstoppers, 148

identification techniques, bugs , 23 ‚ 26

inspection meetings, 111

kickoff activities, 42, 138 ‚ 141

modular, 137

Not Available outcomes, 23

Passes outcomes, 23

phases, list of, 129

play testing

balance, 297 ‚ 300

Beta testing, external, 301 ‚ 302

design changes, 298 ‚ 299

external testing, 300 ‚ 302

overview, 296

post-release, 149

pre-production phase

defect tracking database setup, 134 ‚ 135

draft test plans, 135

lead tester assignment, 133

modular testing, 137

phase acceptance criteria, 133

scope of test, 130 ‚ 132

task planning, 130 ‚ 134

test cases, 137

test steps, 137

test suite, 137

reasons for, 40

regression, 161 ‚ 163

release certification, 148 ‚ 149

sequence of activities, 20

smoke, 161

subject matter, 300 ‚ 301

team responsibilities

Beta testers, 67 ‚ 68

test engineers, 67

test leads, 66, 96

test metrics

progress testing, 171 ‚ 174

TE (Test Effectiveness), 175 ‚ 176

tester performance, 177 ‚ 179

white box, 153 ‚ 155

text

documentation defects, 53

text size standards, 112

TFDs (test flow diagrams)

actions, 212 ‚ 213

allocation activities, 214

in boxes, 219

construction activities, 214 ‚ 216

data dictionary

application use, 226

example of, 226 ‚ 229

overview, 225

reuse, 226

defect trigger examples, 321 ‚ 325

events, 212

example of, 220 ‚ 225

flow components, 211 ‚ 212

preparation activities, 214

primitives, 213

SmartDraw tool examples, 216 ‚ 218

states, 213

templates

craft item, 436

create/save, 437

heal character, 436

overview, 239 ‚ 240

powerups, 435

unlock, 437

terminators, 213

test paths

baseline path generation, 231 ‚ 233

expert path generation, 234 ‚ 235

minimum path generation, 231

overview, 230

strategies, combining, 235 ‚ 236

test case creation from, 236 ‚ 239

usage inversion, cleanroom testing, 263 ‚ 266

when to use, 240

The Crib (ESPN NFL 2K5), 77

The Sims, 291

The Sims Online, 334, 341 ‚ 343

Third Party type selection, DevTrack tool, 34

timing defects, 46 ‚ 47

Tony Hawk's Underground, 317

tool tips, test cases, 158

tracking systems

defect notification, 28 ‚ 35

setup, pre-production test phase, 134 ‚ 135

training techniques, quality, 125 ‚ 126

TRC (Technical Requirements Checklist), 142

triggers, defects

classification, 313 ‚ 315

combinatorial design triggers, 316 ‚ 320

configuration triggers, 309 ‚ 310

Exception, 311 ‚ 312

keywords, 314

Normal, 312 ‚ 313

Restart, 313

Startup, 311

Stress, 312

test designs, 316

TFD trigger examples, 321 ‚ 325

True Crimes: Streets of LA, 24, 64

trust issues

advice from others, 12

arrogance and, 13

conflicts and, 13

emotions and, 10

give and take techniques, 14 ‚ 15

hearsay, 10

low trust levels, 11

publisher/client, 10

strong trust levels, 11

word games, 12

type selection, DevTrack tool, 33 ‚ 34

typographical errors, test case, 158