gathering all viewpoints regarding requirements,
374–375
Power of Three and,
411
using multiple viewpoints in eliciting requirement,
137–138
Visibility, 354–366
code coverage,
360–364
communicating test results,
357–358
defect metrics,
364–366
number of passing tests,
358–360
overview of,
354
release metrics,
358
tracking test tasks and status,
354–357
Visual Studio, 125
Voris, John, 117
W
Waterfall approach, to development
agile development compared with,
12–13
ìmini-waterfallî phenomenon,
46–47
successes of,
112
test plans and,
346
Watir (Web Application Testing in Ruby), 163, 172–174, 320.
Web Services Description Language (WSDL), 507
Web service testing
automating,
282
overview of,
207
Remote Data Monitoring system example,
247–248
tools for,
170–171
WebLoad, 234
Whelan, Declan, 321
Whiteboards
example-driven development,
379
facilitating communication,
430
modeling,
399
planning diagram,
371
reviewing high-level tests with programmers,
400–401
test plan alternatives,
353–354
Whole team approach, 325
advantages of,
26
agile vs. traditional development,
15–16
automation strategy and,
300–301
budget limits and,
55
finding enjoyment in work and,
31
key success factors,
482
,
491
pairing testers with programmers,
279
shared responsibility and,
105–106
team building and,
69
team structure and,
59–62
to test automation,
270
test management and,
322
traditional cross-functional team compared with,
64
value of team members and,
70
Wiki
as communication tool,
164
graphical documentation of examples,
398–399
mockups,
160
,
380
requirements,
402
story checklists and,
156
test cases,
372
traceability and,
88
Wilson-Welsh, Patrick, 278
Wizard of Oz Testing, 138–139
Workflow diagrams, 398
Workload, 393
Worst-case scenarios, 136, 334
Writing tests, strategy for.
WSDL (Web Services Description Language), 507
X
XP (Extreme Programming)
agile team embracing,
10–11
courage as core value in,
25
xUnit, 126–127
Y
Yakich, Joe, 316
Z
Zero bug tolerance, 79, 418–419
