Improvement
approach to process improvement,
448–449
continuous improvement principle,
27–28
ideas for improvement from retrospectives,
447–449
Incremental development
building tests incrementally,
178–179
as core practice,
488
“ilities” tests and,
232
thin slices, small chunks,
144–146
traditional vs. agile testing,
12–13
Index cards, logging bugs on, 423
Infrastructure
Quadrant 1 tests,
111–112
test infrastructure,
319
test plans and,
346–347
Installability testing, 231–232
Installation testing, 461–462
Integrated Development Environments. See IDEs (Integrated Development Environments)
Integration testing
interoperability and,
229
product and external applications,
459
IntelliJ IDEA, 125
Internal quality
measuring internal quality of code,
99
meeting team standards,
366
Quadrant 1 tests and,
111
speed and,
112
Interoperability testing, 228–229
Investment, automation requiring, 267–268
Iteration
automation strategy and,
299–300
definition,
502–503
demo,
443–444
life of a tester and,
327
pre-iteration activities.
See
Pre-iteration activities
prioritizing stories and,
338
review,
415
,
435–437
traditional vs. agile testing,
12–13
Iteration kickoff, 383–403
collaboration with customers,
396–397
considering all viewpoints,
385–389
controlling workload,
393
high-level tests and examples,
397–402
iteration planning,
383–384
learning project details,
384–385
overview of,
383
testable stories,
393–396
writing task cards,
389–392
Iteration metrics, 435–440
defect metrics,
437–440
measuring progress with,
435–437
overview of,
435
usefulness of,
439–440
Iteration planning
considering all viewpoints,
385–389
controlling workload,
393
learning project details,
384–385
overview of,
383–384
writing task cards,
389–392
Iteration review meeting, 415
Iteration wrap up, 443–451
celebrating successes,
449–451
demo of iteration,
443–444
ideas for improvement,
447–449
retrospectives,
444–445
“start, stop, continue” exercise for retrospectives,
445–447
ITIL (Information Technology Infrastructure Library), 90–91
J
JBehave, 165
JConsole, 234
JMeter
performance baseline tests,
235
performance testing,
223
,
234
,
313
JMS (Java Messaging Service)
definition,
502–503
integration with external applications and,
243
testing data feeds and,
249
JProfiler, 234
JUnit
FitNesse as alternative for TDD,
299
functional testing,
176
load testing tools,
234–235
unit test tools,
126
,
165
,
291
JUnitPerf, 234
Just in time development, 369. See also Pre-iteration activities
K
Key success factors
agile testing mind-set,
482–483
automating regression testing,
484
big picture approach,
490–491
coding and testing as one process,
488–489
collaboration with customers,
489–490
continuous integration (CI),
486–487
feedback,
484–486
foundation of core practices,
486
incremental approach (thin slices, small chunks),
488
overview of,
481
synergy between practices,
489
technical debt management,
487–488
test environments,
487
whole team approach,
482
Keyword-driven tests, 182–183
King, Joseph, 176
Knowledge base, DTS, 80–81
Kohl, Jonathan, 201, 204, 211
König, Dierk, 320
L
Language, need for common, 134–135
Layered architecture, 116
Lean measurements, metrics, 74–75
Learning
automation strategy and,
303
continuous improvement principle,
27
Learning curve, automation and, 266–267, 303
Legacy code, 269
Legacy code rescue (Feathers), 117
Legacy systems
ccde,
269
definition,
502–503
logging bugs and,
421
testing,
117
Lessons Learned in Software Testing (Pettichord), 485
Lessons learned sessions, 383. See also Retrospectives
Lightweight processes, 73–74
Lightweight test plans, 350
Load testing. See Performance and load testing
LoadRunner, 234
LoadTest, 234
Logistics, physical, 65–66
LogWatch tool, 212
Loss of identity, QA teams fearing, 44–45
Louvion, Christophe, 63
M
Maintainability testing, 227–228
Management, 52–55
advance clarity and,
373–374
cultural change and,
52–54
overview of,
52
providing metrics to,
440
Managers
cultural changes for,
52–54
how to influence testing,
122–123
speaking managerís language,
55
Manns, Mary Lynn, 121–122
Manual testing
automation vs.,
258–259
peril of,
289
Marcano, Antony, 83, 426
Marick, Brian, 5, 24, 97, 134, 170, 203, 303
Martin, Micah, 169
Martin, Robert C., 169
Matrices
high-level tests and,
398–399
text matrices,
350–353
Maven, 126
McMahon, Chris, 260
Mean time between failure, reliability testing, 230
Mean time to failure, reliability testing, 230
Media, for logging bugs, 423–424
Meetings
demonstrations,
71
,
192
geographically dispersed,
376
iteration kickoff,
372
iteration planning,
23–24
,
244
,
331
,
384
,
389
iteration review,
71
,
415
pre-planning,
370–372
release planning,
338
,
345
retrospective,
447
scheduling,
70
sizing process and,
336–337
standup,
177
,
429
,
462
team participation and,
32
test planning,
263
Memory leaks, 237–238
Memory management testing, 237–238
Meszaros, Gerald, 99, 111, 113, 138, 146, 182, 204, 291, 296, 430
Metrics, 74–79
code coverage,
360–364
communication of,
77–78
defect metrics,
364–366
,
437–440
iteration metrics,
435–440
justifying investment in automation,
268
lean measurements,
74–75
overview of,
74
passing tests,
358–360
reasons for tracking defects,
52
,
75–77
,
82
release metrics,
358
ROI and,
78–79
what not to do with,
77
XP radar charts,
47–48
Milestones, celebrating successes, 449–450
MIME (Multipurpose Internet Mail Extensions)
definition,
504
testing data feeds and,
249
Mind maps, 156–158
Mind-set
agile testing as,
20–21
key success factors,
482–483
pro-active,
369–370
“Mini-waterfall” phenomenon, 46–47
Mock objects
Читать дальше