Agile Testing: A Practical Guide for Testers and Agile Teams

coding and testing simultaneously,

409–410

completing testing tasks,

415–416

identifying variations,

410

managing,

320–322

organizing test results,

322–324

organizing tests,

319–322

planning time for,

455–456

post-development cycles,

467–468

quadrants.

See

Quadrants

release candidates,

458

risk assessment and,

407–409

sustainable pace of,

40–41

traditional vs. agile,

12–15

transparency of tests,

321–322

Testing in context

context-driven testing and,

106–108

definition,

502

TestNG GUI test tool, 127

Tests that never fail, 286

Text matrices, 350–353

The Grinder, 234

Themes. See also Release planning

definition,

507

prioritizing stories and,

339

writing task cards and,

392

Thin slices, incremental development and, 338

Third parties

compatibility testing and,

230

release planning and,

342–344

software,

163

Tholfsen, Mike, 203

Thomas, Mike, 116, 194

Three little pigs metaphor, 278

Timelines, scope and, 340–341

Toolkit (Quadrant 1)

build tools,

126

IDEs,

124–126

overview of,

123

source code control,

123–124

unit test tools,

126–127

Toolkit (Quadrant 2)

API-layer functional test tools,

168–170

automation tools,

164–165

building tests incrementally,

178–179

checklists,

156

flow diagrams,

160–163

GUI test tools,

170–176

keep the tests passing,

179

mind maps,

156–158

mock-ups,

160

software-based tools,

163

spreadsheets,

159

strategies for writing tests,

177–178

test design patterns,

179–183

test management,

186

testability and,

183–185

tool strategy,

153–155

tools for eliciting examples and requirements,

155–156

unit-level test tools,

165–168

Web service test tool,

170

Toolkit (Quadrant 3)

emulator tools,

213–214

monitoring tools,

212–213

simulator tools,

213

user acceptance testing,

250

Toolkit (Quadrant 4)

baselines,

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