Rapid Software Testing with Michael Bolton
Michael Bolton’s Rapid Software Testing Course
Interested in a public / private class? Please submit a query here or contact us at AustralianTesters@gmail.com.
We are very excited to have Michael coming out to Melbourne to present the well known and highly regarded Rapid Software Testing course.
Course Fee $2,600.00 (+GST)
– This class requires a minimum of 15 people to go ahead. Full refund will be provided if the class doesn’t go ahead.
– Refunds can be given (less 25% administration charge) 30 days before the course starts.
Attendees are required to bring a Windows laptop with them.
Course starts promptly at 9am each day, with optional networking from 8:30am.
Morning tea, lunch and afternoon tea will be provided.
This unique 3-day course introduces you to Rapid Software Testing, the skill of testing any software, any time, under any conditions, such that your work stands up to scrutiny. Based on the ideas of James Bach, Michael Bolton, and Cem Kaner, with substantial contributions by other members of the Context-Driven School of software testing, this is the closest thing in the business to a martial art of software testing.
Because we emphasise exercises, it is challenging for experienced testers, but works for new testers, too.
This course provides hands-on demonstrations and drills as well as portable heuristics that help you create tests quickly.
What is Rapid Testing?
Rapid testing is a complete methodology designed for a world of barely sufficient resources, information, and time. It’s an approach to testing that begins with developing personal skills and extends to the ultimate mission of software testing: lighting the way of the project by evaluating the product. The approach is consistent with and a follow-on to many of the concepts and principles introduced in the book Lessons Learned in Software Testing: a Context-Driven Approach by Kaner, Bach, and Pettichord.
The rapid approach isn’t just testing with a speed or sense of urgency; it’s mission-focused testing that eliminates unnecessary work, assures that everything necessary gets done, and constantly asks what testing can do to help speed the project as a whole.
One important tool of rapid testing is the discipline of exploratory testing—essentially a testing martial art. Exploratory testing combines test design, test execution, test result interpretation, and learning into a simultaneous, seamless process that finds a lot of problems quickly. Read more about exploratory testing here.
How Is This Course Different?
Rapid Software Testing is an intensive three-day, hands-on class, in which you spend much of the time actually testing, working on exercises, puzzles, thought experiments, and scenarios—some computer-based, some not. The goal of the course is to teach you how to test anything expertly, under extreme time pressure and conditions of uncertainty, in a way that will stand up to scrutiny.
The philosophy presented in this class is not like traditional approaches to testing, which ignore thethinking part of testing and instead focus on narrow definitions for testing terms while advocating never-ending paperwork. Products have become too complex for that, time is too short, and testers are too expensive. Rapid testing uses a cyclic approach and heuristic methods to constantly re-optimize testing to fit the needs of your clients.
We also offer an optional, free fourth day whose agenda is set by the client. The fourth day can be used for consulting, coaching, conversations with managers or developers, or hands-on testing; whatever you like.
What Will We Learn?
If you are an experienced tester, you’ll find out how to articulate those intellectual processes of testing that you already practice intuitively. If you’re a new tester, hands-on testing exercises will help you gain critical experience.
What If We Outsource?
We have taught this class all over the world to offshore and outsource organizations on behalf of clients who want their testers to do a better job of testing, right away, without needing detailed test procedures. The rapid testing methodology is about getting a lot of value for the testing dollar—value that simply can’t be reproduced by throwing untrained bodies at the problem—so that your top management won’t see testing as a rote activity that any stranger can do as well as you can. If you do outsource, you will need a core team of testers back at headquarters who can rapidly test products to check the “testing” done by outsource firms.
What If We Work In A Regulated Environment?
The basis of the context-driven approach, to which we subscribe, is to begin by addressing the needs of the project. Rapid testing is entirely compatible with that. We have taught this class to organizations pursuing the CMM, and in organizations subject to FDA and other regulatory requirements. Rapid testing is about thinking, so as long as the project owners still want you to think well and find important problems quickly, this is a class that applies to you. We don’t advocate eliminating documentation unless it’s wasteful and irrelevant. Yet we do advocate a lean form of test documentation, trimming it to the greatest extent you can while still fulfilling your project’s mission.