Crispin, Lisa - Agile Testing - A Practical Guide for Testers and Agile Teams

235–237

performance and load testing tools,

234–235

Tools

API-layer functional test tools,

168–170

automation,

164–165

data generation,

304–305

defect tracking,

83–85

eliciting examples and requirements,

155–156

,

159–163

emulator tools,

213–214

exploratory testing,

210–211

generating test data,

212

GUI test tools,

170–176

home-brewed,

175

home-grown,

314

IDEs,

124–126

load testing,

234–235

monitoring,

212–213

open source,

172

,

314–315

performance testing,

234–235

for product owners and business experts,

134

security testing,

225

simulators,

213

software-based,

163

unit-level tests,

126–127

,

165–168

vendor/commercial,

315–316

web service test tool,

170

Tools, automation

agile-friendly,

316

applying one tool at a time,

312–313

home-brewed,

175

home-grown,

314

identifying tool requirements,

311–312

open source,

314–315

selecting,

294–298

vendors,

315–316

Traceability

DTS and,

82

matrices,

86

test planning and,

88

Tracking, test tasks and status, 354–357

Traditional processes, transitioning. See Transitioning traditional processes to agile

Traditional teams, 9–10

Traditional vs. agile testing, 12–15

Training

as deliverable,

469

lack of,

45

Transitioning traditional processes to agile, 73–93

defect tracking.

See

Defect tracking

existing process and,

88–92

lean measurements,

74–75

lightweight processes and,

73–74

metrics and,

74–79

overview of,

73

test planning.

See

Test planning

U

UAT (user acceptance testing)

post-development testing cycles,

467–468

product delivery and,

464–466

in Quadrant 3,

102

release planning for,

331

,

346

Remote Data Monitoring system example,

250

in test plan,

351

tryng out new features and,

102

writing at iteration kickoff meeting,

372

UI (user interface). See also GUI (graphical user interface)

automation strategy and,

293

modeling and,

399

Unit test tools, 165–168. See also by individual unit tools

behavior-driven development tools,

166–168

list of,

126–127

overview of,

165

Unit testing

automating,

282

BDD (Behavior-driven development),

165–168

definition,

507

metrics and,

76

supporting function of,

5

TDD (test-driven development) and,

111

technology-facing tests,

120

tools for Quadrant 1 tests,

126–127

Usability testing, 202–204

checking out applications of competitors,

204

navigation and,

204

overview of,

202

users needs and persona testing,

202–204

what should not be automated,

285–286

Use cases, 398

User acceptance testing. See UAT (user acceptance testing)

User documentation, 207–208

User interface (UI). See also GUI (graphical user interface)

automation strategy and,

293

modeling and,

399

User story.

See

Story

User story card.

See

Story card

User Stories Applied for Agile Software Development (Cohn), 155

V

Vaage, Carol, 330

Value

adding,

31–33

delivering to customer,

22–23

focusing on,

341–342

testers adding,

12

Values, agile, 3–4. See also Principles, for agile testers

Variations, coding and testing and, 410

Velocity

automation and,

255

,

484

burnout rate and,

79

database impact on,

228

defects and,

487

definition,

507

maximizing,

370

sustainable pace of testing and,

41

taking time to do it right,

301

technical debt and,

106

,

313

,

418

,

506

Vendors

automation tools,

315–316

capture-playback tool,

267

IDEs,

125

planning and,

342–344

source code control tools,

124

working with,

142

,

349

Veragen, Pierre, 76, 163, 179, 295, 363, 372, 444

Version control, 123–124, 186. See also Source Code Control

Viewpoints. See also Big picture

considering all viewpoints during iteration planning,

385–389

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. See also Ruby with Watir

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

Working Effectively With Legacy Code (Feathers), 117, 288

Workload, 393

Worst-case scenarios, 136, 334

Writing tests, strategy for. See Strategy, for writing tests

WSDL (Web Services Description Language), 507

X

XP (Extreme Programming)

agile team embracing,

10–11

Читать дальше