Want to learn more about RST? Start with About RST, where we provide material and links internal to this site. Then see the curated list below, consisting mostly of foundational articles about RST by James Bach and Michael Bolton. These articles provide an overview of the RST methodology, and can help you to prepare before attending an RST class. There is also a page of video highlights from the class.
You can find much more information about RST on the sites and blogs of James Bach (satisfice.com) and Michael Bolton (developsense.com).
What skills and tactics are important in testing? Where you start in evaluating the quality of a tester’s work, or of a testing team? Here’s a concise list of the skills, dynamics, and work products of excellent testing, created by … Learn more
RST is a context-driven methodology. This means the our classes are not specifically about testing in an Agile, DevOps, Lean, Waterfall, or regulated context; nor does it incorporate any specific testing tool you might use to simulate users or support … Learn more
We call what we do Rapid Software Testing. About RST Why do we test? We test to develop a comprehensive understanding of the product and the risks around it. We test to find problems that threaten the value of the … Learn more
A statement of the premises on which Rapid Software Testing—our classes and our methodology—are based. These are the premises of the Rapid Software Testing methodology. Everything in the methodology derives in some way from this foundation. These premises derive from our experience, study, … Learn more
RST Peer Advisor Marius Francu has created a YouTube playlist of insights from the online RST Explored and RST Applied classes. For those who haven’t yet taken a class, these offer a little taste of some of the lessons that … Learn more
Bug reporting is central to testing. The bug report, whether oral or written, is the single most visible outcome of testing. And the quality of your reports is probably the single most important factor that determines your credibility as a … Learn more
Back in the year 2000, a company hired me to help them develop a professional testing culture. As part of that process, I found a team of highly regarded testers and studied their approach to bug investigation. Part of what … Learn more
REQUIREMENTS REVISITED In generally accepted software development practice, requirements analysis is supposed to happen before design, and design is supposed to happen before coding and testing. Some kind of document is supposed to come out of requirements analysis. The IEEE … Learn more
To test is to tell three parallel stories: a story of the product, a story of our testing, and a story of the quality of our testing. James and I believe that test framing is a key skill that helps us to compose, edit, … Learn more
Test session reports are a part of session-based test management. This is a checklist for helping you make a good test session report.
Do you perform any exploratory testing on APIs? How do you do it? Here’s an in-depth version of the reply I gave, with the benefit of links to deeper material. To begin: application programming interfaces (APIs) are means by which … Learn more
In Rapid Testing (and, we believe, in all worthwhile testing) learning about the product and finding problems that matter are central to the mission. In the role of a tester, I support the business and development team by finding and describing things I believe … Learn more
At the beginning of the project, you don’t yet know how to test it. To develop a relevant test strategy, you must learn the product. There may be many ways for you to learn about the product—by attending meetings, talking to … Learn more