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

Quadrant 2. See Business-facing tests, supporting team (Quadrant 2)

Quadrant 3. See Business-facing tests, critiquing the product (Quadrant 3)

Quadrant 4. See Technology-facing tests, critiquing the product (Quadrant 4)

Quadrants

automation test categories,

274–276

business facing (Q2 & Q3),

97–98

context-driven testing and,

106–108

critiquing the product (Q3 & Q4),

104

managing technical debt,

106

overview of,

97–98

as planning guide,

490

purpose of testing and,

97

Quadrant 1 summary,

99

Quadrant 2 summary,

99–100

Quadrant 3 summary,

101–102

Quadrant 4 summary,

102–104

shared responsibility and,

105–106

story completion and,

104–105

supporting the team (Q1 & Q2),

100–101

technology facing (Q1 & Q4),

97–98

Quality

customer role in setting quality standards,

26

models,

90–93

organizational philosophy regarding,

38–40

Quality assurance. See QA (quality assurance)

Quality police mentality, 57

Questions, for eliciting requirements, 135–136

R

Radar charts, XP, 47–48

Rasmusson, Jonathan, 11

Record/playback tools

automation strategy and,

294

,

296–297

GUI test tools,

171–172

Recovery testing, 459

Redundancy tests, 232

Reed, David, 171, 377

Refactoring

definition,

504

IDEs supporting,

124–126

Regression suite, 434

Regression tests, 432–434

automated regression tests as a safety net,

261–262

automating as success factor,

484

checking big picture,

434

definition,

504

exploratory testing and,

212

keeping the build “green,”

433

keeping the build quick,

433–434

logging bugs and,

420

regression suite and,

434

release candidates and,

458

Release

acceptance criteria,

470–473

end game,

327

,

456–457

management,

474

product delivery,

470

what if it is not ready,

463–464

Release candidates

challenging release candidate builds,

473

definition,

505

testing,

458

Release metrics

code coverage,

360–364

defect metrics,

364–366

overview of,

358

passing tests,

358–360

Release notes, 474

Release planning, 329–367

overview of,

329

prioritizing and,

338–340

purpose of,

330–331

scope,

340–344

sizing and,

332–337

test plan alternatives,

350–354

test planning,

345–350

visibility and,

354–366

Reliability testing

overview of,

230–231

Remote Data Monitoring system example,

250–251

Remote Data Monitoring system example

acceptance tests,

245

application,

242–243

applying test quadrants,

252–253

automated functional test structure,

245–247

documenting test code,

251

embedded testing,

248

end-to-end tests,

249–250

exploratory testing,

248–249

overview of,

242

reliability testing,

250–251

reporting test results,

251

team and process,

243–244

testing data feeds,

249

unit tests,

244–245

user acceptance testing,

250

web services,

247–248

Remote team member. See Geographically dispersed teams

Repetitive tasks, automating, 284

Reports

documentation and,

208–210

Remote Data Monitoring system example,

251

Repository, 124

Requirements

business-facing tests addressing,

130

documentation of,

402

gathering all viewpoints regarding requirements,

374–375

how to elicit,

135–140

nonfunctional,

218–219

quandary,

132–134

tools for eliciting examples and requirements,

155–156

Resources

completing stories and,

381

hiring agile tester,

67–69

overview of,

66

tester-developer ratio,

66–67

testing and,

434–435

Response time

API,

411

load testing and,

234–235

measurable goals and,

76

web services and,

207

Retrospectives

continuous improvement and,

28

ideas for improvement,

447–449

iteration planning and,

383

overview of,

444–445

process improvement and,

90

“start, stop, and continue” exercise,

445–447

Return on investment. See ROI (return on investment)

Rewards, performance and, 70–71

Rich-client unit testing tools, 127

Rising, Linda, 121–122

Risk

risk analysis,

198

,

286

,

290

,

345–346

risk assessment,

407–409

test mitigating,

147–149

Rogers, Paul, 242, 310, 388, 398

ROI (return on investment)

automation and,

264

definition,

505

lean measurement and,

75

metrics and,

78–79

speaking managerís language,

55

Role, function, business value pattern, 155

Roles

conflicting or multiple roles,

45

cultural differences among,

48–49

customer team,

7

developer team,

7–8

interaction of,

8

RPGUnit, 118

RSpec, 165, 318

Ruby Test::Unit, 170

Ruby with Watir

functional testing,

247

GUI testing,

285

identifying defects with,

212

keywords or actions words for automating tests,

182

overview of,

172–174

test automation with,

186

RubyMock, 127

Rules, managing bugs and, 425

S

Safety tests, 232

Santos, Rafael, 448

Satisfaction conditions. See Conditions of satisfaction

Scalability testing, 233–234

Scenario testing, 192–193

flow diagrams and,

194–195

overview of,

192–195

soap opera tests,

193

Scope, 340–344

business-facing tests defining,

134

deadlines and timelines and,

340–341

focusing on value,

341–342

overview of,

340

system-wide impact,

342

test plans and,

345

third-party involvement and,

342–344

Scope creep, 385, 412

Scripts

automating comparisons,

283

as automation tools,

297

conversion scripts,

461

data generation tools,

305

exploratory testing and,

211–212

Scrum

product owner role,

141

,

373

Remote Data Monitoring system example,

244

sprint reviews,

444

ScrumMaster

approach to process improvement,

448–449

sizing stories and,

336–337

writing task cards and,

391

SDD (story test-driven development)

identifying variations,

410

overview of,

262–263

test-first development and,

263

testing web services and,

170

Security testing

outside-in approach of attackers,

225

overview of,

223–227

specialized knowledge required for,

220

Selenium

GUI test tools,

174–175

implementing automation,

316–318

open source tools,

163

test automation with,

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