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

186

,

316

Self-organization

principles,

29–30

self-organizing teams,

69

Session-based testing, 200–201

Setup

automating,

284–285

exploratory testing,

211–212

Shared resources

access to,

43

specialists as,

301

writing tasks and,

390

Shared responsibility, 105–106

Shout-Out Shoebox, 450

“Show me,” collaboration with programmers, 413–414

Simplicity

automation and,

298–299

coding,

406

logging bugs and,

428–429

principle of “keeping it simple,”

26–27

Simulator tools

embedded testing and,

248

overview of,

213

Size, organizational, 42–43

Sizing stories, 332–337

example of,

334–337

how to,

332–333

overview of,

332

tester’s role in,

333–334

Skills

adaptability and,

39–40

vs. attitude,

20

continuous improvement principle,

27

who performs tests and,

220–221

Small chunks, incremental development, 144–146

SOAP

definition,

505

performance tests and,

223

,

234

Soap opera tests, 193

soapUI

definition,

505

performance tests and,

223

,

234

testing Web Services,

170–171

SOATest, 234

Software-based tools, 163

Software Configuration Management Patterns: Effective Teamwork, Practical Integrations (Berczuk and Appleton), 124

Software Endgames (Galen), 471

Source code control

benefits of,

255

overview of,

123–124

tools for,

124

,

320

SOX compliance, 469

Speak with one voice, customers, 373–374

Specialization, 220–221

Speed as a goal, 112

Spikes, development and test, 381

Spreadsheets

test spreadsheets,

353

tools for eliciting examples and requirements,

159

Sprint reviews, 444. See also Demos/demonstrations

SQL*Loader, 460

Stability testing, 28

Staging environment, 458

Stand-up meetings, 177, 429, 462

Standards

maintainability and,

227

quality models and,

90–93

“Start, stop, continue” exercise, retrospectives, 445–447

Static analysis, security testing tools, 225

Steel thread, incremental development, 144, 338, 345

Stories. See also Business-facing tests

benefits of working on in advance of iterations,

370–372

briefness of,

129–130

business-facing tests as,

130

determining story size,

375–376

focusing on one story when coding,

411–412

identifying variations,

410

knowing when a story is done,

104–105

logging bugs and,

420–421

mock-ups and,

380

prioritizing,

338–340

resources and,

381

scope and,

340

sizing.

See

Sizing stories

starting simple,

133

,

406

story tests defined,

505

system-wide impact of,

342

test plans and,

345

test strategies and,

380–381

testable,

393–396

treating bugs as,

425

Story boards

burndown charts,

429

definition,

505–506

examples,

356–357

online,

357

,

384

physical,

356

stickers and,

355

tasks,

222

,

355

,

436

virtual,

357

,

384

,

393

work in progress,

390

Story cards

audits and,

89

dealing with bugs and,

424–425

iteration planning and,

244

story narrative on,

409

Story test-driven development. See SDD (story test-driven development)

Strangler application (Fowler), 116–117

Strategy

automation.

See

Automation strategy

test planning vs. test strategy,

86–87

test strategies,

380–381

Strategy, for writing tests

building tests incrementally,

178–179

iteration planning and,

372

keep the tests passing,

179

overview of,

177–178

test design patterns,

179–183

testability and,

183–185

Stress testing. See Load testing

Subversion (SVN), 124, 320

Success factors. See Key success factors

Successes, celebrating

change implementation and,

50–52

iteration wrap up and,

449–451

Sumrell, Megan, 365, 450

Sustainable pace, of testing, 40–41, 303

SVN (Subversion), 124, 320

SWTBot GUI test tool, 127

Synergy, between practices, 489

System, system-wide impact of story, 342

T

tail-f, 212

Tartaglia, Coni, 439, 454, 470, 473

Task boards. See Story boards

Task cards

automating testing and,

394–395

iteration planning and,

389–392

product delivery and,

462–463

Tasks

completing testing tasks,

415–416

definition,

505–506

TDD (test-driven development)

automated tests driving,

262–263

defects and,

490

definition,

506

overview of,

5

Test-First Development compared with,

113–114

unit tests and,

111

,

244–245

Team City, 126

Team structure, 59–65

agile project teams,

64–65

independent QA team,

60

integration of testers into agile project,

61–63

overview of,

59

traditional functional structure vs agile structure,

64

Teams

automation as team effort,

484

building,

69–71

celebrating success,

50–52

co-located,

65–66

controlling workload and,

393

customer,

7

developer,

7–8

empowerment of,

44

facilitating communication and,

429–432

geographically dispersed,

376–378

,

431–432

giving all team members equal weight,

31

giving ownership to,

50

hiring agile tester for,

67–69

interaction between customer and developer teams,

8

iteration planning and,

384–385

logistics,

59

problem solving and,

123

Remote Data Monitoring system example,

243–244

shared responsibility and,

105–106

traditional,

9–10

using tests to support Quadrants

1

and

2

,

100–101

whole team approach.

See

Whole team approach

working on agile teams,

10–12

Teardown, for tests, 307–308

Technical debt

defects as,

418

definition,

506

managing,

106

,

487–488

Technology-facing tests

overview of,

5

Quadrants 1 & 4,

97–98

Technology-facing tests, critiquing the product (Quadrant 4), 217–239

baselines,

235–237

coding and testing and,

412–413

compatibility testing,

229–230

installability testing,

231–232

interoperability testing,

228–229

maintainability testing,

227–228

memory management testing,

237–238

overview of,

217–219

performance and load testing,

234

performance and load testing tools,

234–235

reliability testing,

230–231

,

250–251

scalability testing,

233–234

security testing,

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