Agile Testing: A Practical Guide for Testers and Agile Teams

starting simple and then adding complexity,

406–407

test cases for,

137

Embedded system, Remote Data Monitoring example, 248

Empowerment, of teams, 44

Emulator tools, 213–214

End game

Agile testing,

91

iteration,

14

product delivery and,

456–457

release and,

327

End-to-end tests, 249–250

Enjoyment, principle of, 31

Environment, test environment, 347–348

Epic. See also Themes

definition,

502

features becoming,

502

iterations in,

76

,

329

planning,

252

ePlan Services, Inc., xli, 267

Errors, manual testing and, 259

Estimating story size, 332–338

eValid, 234

Event-based patterns, test design patterns, 181

Everyday Scripting with Ruby for Teams, Testers, and You (Marick), 297, 303

Example-driven development, 378–380

Examples

for eliciting requirements,

136–137

tools for eliciting examples and requirements,

155–156

Executable tests, 406

Exploratory testing (ET)

activities, characteristics, and skills (Hagar),

198–200

attributes of exploratory tester,

201–202

automation of,

201

definition,

502–503

end game and,

457

explained (Bolton),

195–198

manual testing and,

280

monitoring tools,

212

overview of,

26

,

195

Remote Data Monitoring system example,

248–249

session-based testing and,

200–201

setup,

211–212

simulators and emulators,

212–213

tests that critique the product,

412–413

tools for,

210–212

tools for generating test data,

212

what should not be automated,

286

External quality, business facing tests defining, 99, 131

External teams, 43, 457

Extreme Programming. See XP (Extreme Programming)

Extreme Programming Explained (Beck), 26

F

Face-to-face communication, 23–25

Failover tests, 232

Failure, courage to learn from, 25

Fake objects, 115, 118, 306, 502–503

Fault tolerance, product delivery and, 459

Fear

barriers to automation,

269–270

change and,

49–50

Fearless Change (Manns and Rising), 121

Feathers, Michael, 117, 288

Features

defects vs.,

417–418

definition,

502–503

focusing on value,

341

Feedback

automated tests providing,

262

continuous feedback principle,

22

iterative approach and,

299–300

key success factors,

484–486

managing tests for,

323–324

Quadrant 1 tests and,

118–119

“Fit and finish” deliverables, 454

Fit (Framework for Integrated Test), 134–135

API-layer functional test tools,

168–169

automation test pyramid and,

278

FIT IssueTrack, Alcea, 83–84

FitNesse

advantages of,

163

API-layer functional test tools,

169–170

automating functional tests with,

30

,

145

business-facing tests with,

154

,

178

collaboration and,

164

continual builds and,

119

,

357

data verification with,

287

doneness and,

472

encouraging use of,

122

examples and,

136

,

169

feedback and,

323–324

file parsing rules illustrated with,

205

functional testing behind the GUI,

291

,

300

home-grown scripts and,

305

JUnit compared with,

299

keywords or actions words for automating tests,

182–183

manual vs. automated testing,

210

memory demands of,

306

organizing tests and,

319–320

overview of,

168–170

remote testing and,

432

“start, stop, continue” list,

446

support for source code control tools,

320

test automation pyramid and,

278

test cards and,

389–390

test cases as documentation,

402

test design and maintenance,

292

testing database layer with,

284

testing stories,

395

traceability requirements and,

88

user acceptance testing,

295

wikis and,

186

Fleisch, Patrick, 377, 440

Flow diagrams

scenario testing and,

194–195

tools for eliciting examples and requirements,

160–163

Fowler, Martin, 117

Framework for Integrated Test. See Fit (Framework for Integrated Test)

Frameworks, 90–93

ftptt, 234

Functional analysts, 386

Functional testing

compatibility issues and,

230

definition,

502–503

end-to-end tests,

249–250

layers,

246

nonfunctional tests compared with,

225

Remote Data Monitoring system example,

245–247

G

Galen, Bob, 455–456, 471

Gärtner, Markus, 395, 476

Geographically dispersed teams

coping with,

376–378

facilitating communication and,

431–432

Gheorghiu, Grig, 225–226, 234

Glover, Andrew, 166

Greenfield projects

code testing and,

116

definition,

502–503

GUI (graphical user interface)

automation strategy and,

293

code flux and,

269

standards,

227

GUI smoke tests

Canoo WebTest and,

300

continual builds and,

119

defect metrics,

437

GUI test tools, 170–176

Canoo Web Test,

174–175

“home-brewed” test automation tools,

175

open source test tools,

172

overview of,

170–171

record/playback tools,

171–172

Ruby with Watir,

172–174

Selenium,

174

GUI testing

API testing,

205–206

automating,

282–283

,

295–296

automation test pyramid and,

278

GUI smoke tests,

119

,

300

,

437

overview of,

204

Web service testing,

207

H

Hagar, Jon, 198

Hardware

compatibility and,

229

cost of test environments,

487

functional testing and,

230

investing in automation and,

267

production environment and,

310

scalability and,

233

test infrastructure,

319

testing product installation,

462

Hendrickson, Elisabeth, 203, 315–316

High-level test cases, 397–402

mockups,

398–399

overview of,

397–398

reviewing with customers,

400

reviewing with programmers,

400–401

test cases as documentation,

402

Hiring a tester, 67–69

Holzer, Jason, 220, 448

Home-grown test tool

automation tools,

314

GUI test tools,

175

test results,

323

httperf, 234

Hudson, 126

I

IBM Rational ClearCase, 124