Abstract: Implementing a feature in a two week timebox is easy enough: Reduce scope to a few small changes. The real problem comes when we try to compress testing from months to a day or two.
It is possible, but it will take a lot more than stories, sprints, and standups. The whole team will need to work together, to figure out what to build before we build it, to check for and ensure quality is high at every step, instead of letting uncertainty rise and conducting a mass inspection at the end. Learn to put down old tools, like test cases, test plans, and test strategy documents, along with what to pick up in their place - Exploration, Specification by Example, Unit tests, Build and Deploy automation.
Matt Heusser describes this new way of thinking about testing, how it changes the way we work, and where to go to keep going.
Learning Outcomes: - Understand why traditional testing fails in an Agile Environment
- Understand how frequent delivery changes the way software is built and tested
- Compare whole-team quality to QA as gatekeeper
- Understand the impact of first-time quality on a release
- Understand why traditional attempts to build quality in failed, and how Agile Quality is different
- Understand Exploratory testing, tooling, and unit tests (TDD), Continuous Integration, and how the four play off each other
- Know where to go to get started
Attachments:
