conflicting or multiple roles,
45
cultural differences among roles,
48–49
lack of training,
45
lack of understanding of agile concepts,
45–48
loss of identity,
44–45
overview of,
44
past experience and attitudes,
48
Baselines
break-test baseline technique,
363
performance,
235–237
Batch
files,
251
processing,
345
scheduling process,
182
BDD (Behavior-driven development)
easyb tool,
166–168
tools for Quadrant 1 tests,
127
Beck, Kent, 26, 99
Benander, Mark, 51
Benchmarking, 237
Berczuk, Stephen, 124
Beta testing, 466–467
Big picture
agile testers focus on,
23
high-level tests and examples,
397–402
key success factors,
490–491
peril of forgetting,
148
regression tests and,
434
Bolton, Michael, 195
Bos, Erik, 114
Boundary conditions
API testing and,
205
automation and,
11
data generation tools and,
304
identifying test variations,
410
writing test cases for,
137
Boyer, Erika, 140, 163, 372, 432
Brainstorming
automation giving testers better work,
260
prior to iteration,
370
,
381
quadrants as framework for,
253
taking time for,
301
testers,
121
Break-test baseline technique, 363
Browsers, compatibility testing and, 230
Budget limits, 55
Bug tracking. See Defect tracking
Bugs. See Defects
Build
automating,
280–282
challenging release candidate builds,
473
definition,
501
incremental,
178–179
speeding up,
118–119
Build automation tools, 126, 282
Build/Operate/Check pattern, 180
Build tools, 126
BuildBeat, 126
Business analysts, 374
Business expert role
agreement regarding requirements,
428
,
430
common language and,
134
,
291
,
414
on customer team,
6–7
iteration demo and,
443
language of,
291
Power of Three and,
482
tools geared to,
134
Business-facing tests
agile testing as,
6
Quadrants 2 & 3,
97–98
technology-facing tests compared with,
120
Business-facing tests, critiquing the product (Quadrant 3), 189–215
acceptance tests,
245
API testing,
205–206
demonstrations,
191–192
emulator tools,
213–214
end-to-end tests,
249–250
exploratory testing,
195–202
,
248–249
generating test data,
212
GUI testing,
204
monitoring tools,
212–213
overview of,
189–191
reports,
208–210
scenario testing,
192–195
session-based testing,
200–201
setting up tests,
211–212
simulator tools,
213
tools for exploratory testing,
210–211
usability testing,
202–204
user acceptance testing,
250
user documentation,
207–208
web services testing,
207
Business-facing tests, supporting team (Quadrant 2), 129–151
advance clarity,
140–142
automating functional tests,
245–247
common language and,
134–135
conditions of satisfaction and,
142–143
doneness,
146–147
driving development with,
129–132
eliciting requirements,
135–140
embedded testing,
248
incremental approach,
144–146
requirements quandary and,
132–134
ripple effects,
143–144
risk mitigation and,
147–149
testability and automation,
149–150
toolkit for.
See
Toolkit
(Quadrant 2)
web services testing,
247–248
Business impact, 475–476
Business value
adding value,
31–33
as goal of agile development,
5–8
,
69
,
454
metrics and,
75
release cycles and,
3
role, function, business value pattern,
155
team approach and,
16
Busse, Mike, 106, 235, 284, 313
Buwalda, Hans, 193
C
Canonical data, automating databases and, 308–309
Canoo WebTest
automating GUI tests,
184
,
186
GUI regression test suite,
291
GUI smoke tests,
300
GUI test tools,
174–175
organizing tests and,
320
scripts and,
320
XML Editor for,
125
Capability Maturity Model Integration (CMMI), 90–91
Capture-playback tool, 267
Celebrating successes
change implementation and,
50–52
iteration wrap up and,
449–451
Chandra, Apurva, 377
Chang, Tae, 53–54
Change
celebrating successes,
50–52
giving team ownership,
50
introducing,
49
not coming easy,
56–57
responsiveness to,
28–29
talking about fears,
49–50
Checklists
release readiness,
474
tools for eliciting examples and requirements,
156
CI. See Continuous integration (CI)
CI Factory, 126
CMMI (Capability Maturity Model Integration), 90–91
Co-location, team logistics and, 65–66
Coaches
adjusting to agile culture and,
40
learning curve and,
266
providing encouragement,
69
skill development and,
122
training and,
45–46
Cockburn, Alistair, 115
Code
automation and code flux,
269
automation and legacy code,
269
automation strategy and,
303–304
documentation of,
251
standards,
227
writing testable,
115
Code coverage, release metrics, 360–364
Coding and testing, 405–441
adding complexity,
407
alternatives for dealing with bugs,
424–428
choosing when to fix bugs,
421–423
collaborating with programmers,
413–414
dealing with bugs,
416–419
deciding which bugs to log,
420–421
driving development and,
406
facilitating communication,
429–432
focusing on one story,
411–412
identifying variations,
410
iteration metrics,
435–440
media for logging bugs,
423–424
overview of,
405
Power of Three for resolving differences in viewpoint,
411
regression testing and,
432–434
resources,
434–435
risk assessment,
407–409
as simultaneous process,
409–410
,
488–489
starting simple,
406
,
428–429
talking to customers,
414–415
tests that critique the product,
412–413
Cohn, Mike, 50, 155, 276, 296, 331, 332
Collaboration
with customers,
396–397
key success factors,
489–490
with programmers,
413–414
whole team approach,
15–16
Collino, Alessandro, 103, 363
Communication
common language and,
134–135
with customer,
140
,
396–397
DTS (Defect Tracking System) and,
83
facilitating,
23–25
,
429–432
product delivery and,
462–463
size as challenge to,
42–43
between teams,
69–70
test results,
357–358
Comparisons, automating, 283
Compatibility testing, 229–230
Читать дальше