definition,
504
risk alleviation and,
459
tools for implementing,
127
unit tests and,
114
Mock-ups
facilitating communication and,
430
high-level tests and,
398–399
stories and,
380
tools for eliciting examples and requirements,
160
Model-driven development, 398
Models
quality models,
90–93
UI modeling example,
399
Monitoring tools, 212–213, 235
Multi-layered approach, automation strategy, 290–292
Multipurpose Internet Mail Extensions (MIME)
definition,
504
testing data feeds and,
249
N
Naming conventions, 227
Nant, 126
Navigation, usability testing and, 204
NBehave, 165
NeoLoad, 234
Nessus, vulnerability scanner, 226
.NET Memory Profiler, 234
NetBeans, 125
NetScout, 235
Non-functional testing. See also Technology-facing tests, critiquing the product (Quadrant 4)
delivering product and,
458–459
functional testing compared with,
225
requirements,
218–219
when to perform,
222
North, Dan, 165
NSpec, 165
NUnit, 126, 165
O
Oleszkiewicz, Jakub, 418
One-off tests, 286–287
Open source tools
agile open source test tools,
172–175
automation and,
314–315
GUI test tools,
172
IDEs,
124–125
OpenWebLoad, 234
Operating systems (OSs), compatibility testing and, 230
Organizations, 37–44
challenges of agile development,
35
conflicting cultures,
43
customer relationships and,
41–42
overview of,
37–38
quality philosophy,
38–40
size and,
42–43
sustainable pace of testing and,
40–41
team empowerment,
44
OSs (operating systems), compatibility testing and, 230
Ownership, giving team ownership, 50
P
Packaging, product delivery and, 474–475
Pair programming
code review and,
227
developers trained in,
61
IDEs and,
125
team approach and,
244
Pair testing, 413
Passing tests, release metrics, 358–360
PerfMon, 235
Perforce, 124
Performance and load testing
automating,
283
baselines,
235–237
memory management testing,
237–238
overview of,
234
product delivery and,
458
scalability testing,
233–234
test environment,
237
tools for,
234–235
when to perform,
223
who performs the test,
220–221
Performance, rewards and, 70–71
Perils
forgetting the big picture,
148
quality police mentality,
39
the testing crunch,
416
waiting for Tuesdayís build,
280
youíre not really part of the team,
32
Perkins, Steve, 156, 159, 373
PerlClip
data generation tools,
305
tools for generating test data,
212
Persona testing, 202–204
Pettichord, Bret, 175, 264, 485
Phased and gated development, 73–74, 129
Physical logistics, 65–66
Planning
advance,
43
iteration.
See
Iteration planning
release/theme planning.
See
Release planning
testing.
See
Test planning
PMO (Project Management Office), 440
Pols, Andy, 134
Ports and Adapters pattern (Cockburn), 115
Post-development testing, 467–468
Post-iteration bugs, 421
Pounder, 234
Power of Three
business expert and,
482
finding a common language,
430
good communication and,
33
,
490
problem solving and,
24
resolving differences in viewpoint,
401
,
411
whole team approach and,
482
Pragmatic Project Automation , 260
Pre-iteration activities, 369–382
advance clarity,
373
benefits of working on stories in advance,
370–372
customers speaking with one voice,
373–374
determining story size,
375–376
evaluating amount of advance preparation needed,
372–373
examples,
378–380
gathering all viewpoints regarding requirements,
374–375
geographically dispersed team and,
376–378
overview of,
369
prioritizing defects,
381
pro-active mindset,
369–370
resources,
381
test strategies and,
380–381
Pre-planning meeting, 370–372
Principles, automation
agile coding practices,
303–304
iterative approach,
299–300
keep it simple,
298–299
learning by doing,
303
overview of,
298
taking time to do it right,
301–303
whole team approach,
300–301
Principles, for agile testers
continuous feedback,
22
continuous improvement,
27–28
courage,
25–26
delivering value to customer,
22–23
enjoyment,
31
face-to-face communication,
23–25
keeping it simple,
26–27
overview of,
21–22
people focus,
30
responsive to change,
28–29
self-organizing,
29–30
Prioritizing defects, 381
Prioritizing stories, 338–340
Pro-active mindset, 369–370
Product
business value,
31–33
delivery.
See
Delivering product
tests that critique (Q3 & Q4),
101–104
what makes a product,
453–455
Product owner
considering all viewpoints during iteration planning,
386–389
definition,
504
iteration planning and,
384
Scrum roles,
141
,
373
tools geared to,
134
Production
logging bugs and,
421
support,
475
Production code
automation test pyramid and,
277–278
definition,
504
delivering value to,
70
programmers writing,
48
source code control and,
434
synchronization with testing,
322
test-first development and,
113
tests supporting,
303–304
Production-like data, automating databases and, 309–310
Professional development, 57
Profiling tools, 234
Programmers
attitude regarding automation,
265–266
big picture tests,
397
collaboration with,
413–414
considering all viewpoints during iteration planning,
387–389
facilitating communication and,
429–430
reviewing high-level tests with,
400–401
tester-developer ratio,
66–67
testers compared with,
4
,
5
training,
61
writing task cards and,
391
Project Management Office (PMO), 440
Projects, PAS example, 176–177
Prototypes
accessible as common language,
134
mock-ups and,
160
paper,
22
,
138–139
,
380
,
400
,
414
paper vs. Wizard of Oz type,
275
UI (user interface),
107
Pulse, 126
PyUnit unit test tool for Python, 126
Q
QA (quality assurance)
definition,
504
in job titles,
31
independent QA team,
60
interchangeable with “test,”
59
whole team approach,
39
working on traditional teams,
9
Quadrant 1. See Technology-facing tests, supporting team (Quadrant 1)
Читать дальше