Lisa Crispin is an agile testing coach and practitioner. She is the co-author, with Janet Gregory, of Agile Testing: A Practical Guide for Testers and Agile Teams (Addison-Wesley, 2009). She specializes in showing testers and agile teams how testers can add value and how to guide development with business-facing tests. Her mission is to bring agile joy to the software testing world and testing joy to the agile development world. Lisa joined her first agile team in 2000, having enjoyed many years working as a programmer, analyst, tester, and QA director. Since 2003, she’s been a tester on a Scrum/XP team at ePlan Services, Inc. in Denver, Colorado. She frequently leads tutorials and workshops on agile testing at conferences in North America and Europe. Lisa regularly contributes articles about agile testing to publications such as Better Software magazine, IEEE Software, and Methods and Tools. Lisa also co-authored Testing Extreme Programming (Boston: Addison-Wesley, 2002) with Tip House.


For more about Lisa’s work, visit www.lisacrispin.com.
   
Using the Agile Testing Quadrants to Cover Your Testing Needs

Testing is at the core of agile development. We use tests to drive development as well as to ensure we deliver the right business value. Software quality has many dimensions, so we need to complete many different types of tests within a release cycle. Agile development increases the challenges with short iterations and frequent releases.
The Agile Testing Quadrants come to the rescue, providing a helpful way for teams to to categorize, plan and execute all facets of testing. In this interactive tutorial, participants will learn how to use the Agile Testing Quadrants to make sure the team covers all aspects of testing, including programmer-facing tests that aid code design, business-facing tests that help the team deliver the right software, and technology-facing tests that cover non-functional requirements such as performance, security and usability. This tutorial answers questions such as:

  • What are all the different types of testing we need to plan for a given project or release?
  • Who’s responsible for completing each type of testing activity?
  • When, in an agile project, do we do those different types of testing?
  • Which tests should be automated?
  • How do we know when we’re “done” testing?
The tutorial will give special emphasis to using the business-facing tests to support the development team and critique the product.
Agile Testing Days - 2009 - a Díaz & Hilterscheid Conference