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 databaseThe test team now has to figure out how to “go agile”, tooOr, maybe you’re new to a team that has never had a tester or test team beforeDoes 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 processWhere do we start?
Stop the bleedingIdentify frequent and time-consuming tasksBegin to automate themBegin to run them regularly“Hey developer, can youhelp me with this?”
Pair Testing
Start pair-developing (pair tester with dev)Start writing testautomation with newfeaturesRegular builds or continuous integration“Done” means codedand tested (and documented, if needed)Stay Current
Pair Programming
Start to fill in automation of regression testsSome UI testsMany FitNesse/integration testsLOTS OF unittestsBegin to refactor both code and testsCatch 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 Crispinwww.janetgregory.ca – Janet Gregory www.exampler.com - Brian Marick www.testobsessed.com – Elisabeth Hendricksonwww.mountaingoatsoftware.com – Mike Cohngojko.net – GojkoAdzicwww.passionatetester.com – me! www.testingreflections.com Agile Manifesto: http://agilemanifesto.org/Agile Testing References

Testing Legacy Apps

  • 1.
    Testing Legacy AppsDawnCannan, agile tester
  • 2.
    You are atester 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 databaseThe test team now has to figure out how to “go agile”, tooOr, maybe you’re new to a team that has never had a tester or test team beforeDoes this sound familiar?
  • 3.
    So many “types”of testing, and how much of each do we need?What’s the “big picture”?
  • 4.
    Test Automation Pyramid*Pyramid via Mike Cohn
  • 5.
    Agile Testing Quadrants*Quadrants via Lisa Crispin and Janet Gregory
  • 6.
    Mike Cohn describesit well in a 3-step processWhere do we start?
  • 7.
    Stop the bleedingIdentifyfrequent and time-consuming tasksBegin to automate themBegin to run them regularly“Hey developer, can youhelp me with this?”
  • 8.
  • 9.
    Start pair-developing (pairtester with dev)Start writing testautomation with newfeaturesRegular builds or continuous integration“Done” means codedand tested (and documented, if needed)Stay Current
  • 10.
  • 11.
    Start to fillin automation of regression testsSome UI testsMany FitNesse/integration testsLOTS OF unittestsBegin to refactor both code and testsCatch Up
  • 12.
    Test Automation Pyramid(revisited)* Pyramid via Mike Cohn
  • 13.
    Agile Testing Quadrants(revisited)* Quadrants via Lisa Crispin and Janet Gregory
  • 14.
  • 15.
    www.lisacrispin.com – LisaCrispinwww.janetgregory.ca – Janet Gregory www.exampler.com - Brian Marick www.testobsessed.com – Elisabeth Hendricksonwww.mountaingoatsoftware.com – Mike Cohngojko.net – GojkoAdzicwww.passionatetester.com – me! www.testingreflections.com Agile Manifesto: http://agilemanifesto.org/Agile Testing References