Agile Testing: A Practical Guide for Testers and Agile Teams

RpgUnit, RPG Regression Testing Framework, www.RPGunit.org.

Selenium, Web Application Testing System, http://selenium.openqa.org.

soapUI, Web Services Testing Tool, www.soapui.org.

Source Configuration Management, http://better-scm.berlios.de.

Subversion, Open Source Version Control System, http://subversion.tigris.org/.

Unit Testing Frameworks. http://en.wikipedia.org/wiki/List_of_unit_testing_frameworks.

Watir, Web Application Testing in Ruby, http://wtr.rubyforge.org, http://watircraft.com.

Index

A

Abbot GUI test tool, 127

Acceptance tests. See also Business-facing tests

definition,

501

Remote Data Monitoring system example,

245

UAT (user acceptance testing) compared with,

130

Ad hoc testing, 198

Adaptability, skills and, 39–40

ADEPT (AS400 Displays for External Prototyping and Testing), 117–118

Advance clarity

customers speaking with one voice,

373–374

determining story size,

375–376

gathering all viewpoints regarding requirements,

374–375

overview of,

140–142

,

373

Advance preparation

downside of,

373

how much needed,

372–373

Agile development

Agile manifesto and,

3–4

barriers to.

See

Barriers to adopting agile development

team orientation of,

6

Agile Estimating and Planning (Cohn), 331, 332

Agile manifesto

people focus,

30

statement of,

4

value statements in,

21

Agile principles. See Principles, for agile testers

Agile testers. See also Testers

agile testing mind-set,

482–483

definition,

4

giving all team members equal weight,

31

hiring,

67–69

what they are,

19–20

Agile testing

definition,

6

as mind-set,

20–21

what we mean,

4–7

Agile values, 3–4

Alcea’s FIT IssueTrack, 84

Alpha tests, 466–467

ant, 284

as build tool,

126

continual builds and,

175

,

291

AnthillPro, 126

ANTS Profiler Pro, 234

Apache JMeter. See JMeter

API-layer functional test tools, 168–170

Fit and FitNesse,

168–170

overview of,

168

testing web Services,

170

API testing

automating,

282

overview of,

205–206

APIs (application programming interfaces), 501

Appleton, Brad, 124

Application under test (AUT), 246

Applications

integration testing with external applications,

459

Remote Data Monitoring system example,

242–243

Architecture

incremental approach to testing,

114

layered,

116

Quadrant 1 tests and,

99

scalability and,

104

,

221

testable,

30

,

115

,

182

,

184

,

267

AS400 Displays for External Prototyping and Testing (ADEPT), 117–118

Assumptions, hidden

agile testers response to,

25

failure to detect,

32

questions that uncover,

136

worst-case scenarios and,

334

Attitude

agile testing mind-set,

482–483

barriers to adopting agile development,

48

vs. skills,

20

Audits, compliance with audit requirements, 89–90

AUT (application under test), 143, 225, 246, 317

Authorization, security testing and, 224

Automated regression testing

key success factors,

484

release candidates and,

458

as a safety net,

261–262

Automated test lists, test plan alternatives, 353–354

Automation

code flux and,

269

of deployment,

232

driving development with,

262–263

of exploratory testing,

201

fear of,

269–270

feedback from,

262

freeing people for other work,

259–261

of functional test structure,

245–247

home-brewed test,

175

investment required,

267–268

learning curve,

266–267

legacy code and,

269

maintainability and,

227–228

manual testing vs.,

258–259

obstacles to,

264–265

old habits and,

270

overview of,

255

programmers’ attitude regarding,

265–266

reasons for,

257–258

responding to change and,

29

ROI and,

264

task cards and,

394–395

testability and,

149–150

tests as documentation,

263–264

Automation strategy

agile coding practices and,

303–304

applying one tool at a time,

312–313

data generation tools,

304–305

database access and,

306–310

design and maintenance and,

292–294

developing,

288–289

identifying tool requirements,

311–312

implementing,

316–319

iterative approach,

299–300

keep it simple,

298–299

learning by doing,

303

managing automated tests,

319

multi-layered approach to,

290–292

organizing test results,

322–324

organizing tests,

319–322

overview of,

273

principles,

298

record/playback tools and,

294

,

296–297

starting with area of greatest pain,

289–290

taking time to do it right,

301–303

test automation pyramid,

276–279

test categories,

274–276

tool selection,

294–298

,

313–316

understanding purpose of tests and,

310–311

what can be automated,

279–285

what might be difficult to automate,

287–288

what should not be automated,

285–287

whole team approach,

300–301

Automation tools, 164–177

API-layer functional test tools,

168–170

builds and,

126

GUI test tools,

170–176

overview of,

164–165

unit-level test tools,

165–168

web services test tool,

170

B

Bach, James, 195, 200, 212

Bach, Jonathan, 201

Back-end testing

behind the GUI,

282

non-UI testing,

204–205

Bamboo, 126

Barriers to adopting agile development, 44–49

conflicting or multiple roles,

45

cultural differences among roles,

48–49

lack of training,

45

lack of understanding of agile concepts,

45–48

loss of identity,

44–45

overview of,

44

past experience and attitudes,

48

Baselines

break-test baseline technique,

363

performance,

235–237

Batch

files,

251

processing,

345

scheduling process,

182

BDD (Behavior-driven development)

easyb tool,

166–168

tools for Quadrant 1 tests,

127

Beck, Kent, 26, 99

Benander, Mark, 51

Benchmarking, 237

Berczuk, Stephen, 124