Testing, as we’ve pointed out (many times), is not test cases; testing is a performance. Testing, as we’ve pointed out, is the process of learning about a product through exploration and experimentation, which includes to some degree questioning, studying, modeling, observation, inference, etc. … Learn more
This is a process guide for creating a good test plan within the RST methodology. It consists of seven tasks. The tasks can be performed in any order, or simultaneously and iteratively.
The HTSM (v.5.7.5) is a set of guideword heuristics designed to help you think better about test strategy. It includes four focus areas: test techniques, project elements, product elements, and quality criteria categories. You can use it casually or rigorously. … Learn more
This video describes the general structure of the Rapid Software Testing methodology.
This is a detailed explanation of how automation helps us in software testing. We show that automation can do much more than merely simulating a user who is pressing buttons. A downloadable pdf.
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
To test is—among many other things—to construct, edit, narrate, and justify a story. A excellent, expert test report has at least three significant elements that weave around each other like a braid: a story about the product; a story about … 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