Testing Legacy AppsDawn Cannan, agile tester

You are a tester on a team that is “going agile” or has “gone agile”

Most testing has been people manually clicking and typing on the “QA Server”

Bug reports have been filed and many ignored for a while, leading to a huge bug database

The test team now has to figure out how to “go agile”, too

Or, maybe you’re new to a team that has never had a tester or test team before

Does this sound familiar?

So many “types” of testing, and how much of each do we need?

What’s the “big picture”?

Test Automation Pyramid

* Pyramid via Mike Cohn

Agile Testing Quadrants

* Quadrants via Lisa Crispin and Janet Gregory

Mike Cohn describes it well in a 3-step process

Where do we start?

Stop the bleeding Identify frequent and time-consuming tasks Begin to automate them Begin to run them regularly “Hey developer, can youhelp me with this?”

Pair Testing

Start pair-developing (pair tester with dev)

Start writing testautomation with newfeatures Regular builds or continuous integration “Done” means codedand tested (and documented, if needed)

Stay Current

Pair Programming

Start to fill in automation of regression tests

Some UI tests Many FitNesse/integration tests LOTS OF unittests Begin to refactor both code and tests

Catch Up

Test Automation Pyramid (revisited)

* Pyramid via Mike Cohn

Agile Testing Quadrants (revisited)

* Quadrants via Lisa Crispin and Janet Gregory

Collaboration

www.lisacrispin.com – Lisa Crispin www.janetgregory.ca – Janet Gregory www.exampler.com - Brian Marick www.testobsessed.com – Elisabeth

Hendrickson www.mountaingoatsoftware.com – Mike Cohn gojko.net – Gojko Adzic www.passionatetester.com – me! www.testingreflections.com Agile Manifesto: http://agilemanifesto.org/

Agile Testing References