We call what we do Rapid Software Testing.
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 product, or that threaten the on-time, successful completion of any kind of development work. We test to help the business, managers, and developers decide whether the product they’ve got is the product they want.
Above all, we test because it is the responsible thing to do. We have a duty of care toward our teams, our organizations, our customers, and society itself. Releasing poorly tested software would be a breach of that duty.
Rapid Software Testing (RST) is all about that. It is a responsible approach to software testing, centered around people who do testing and people who need it done. It is a methodology (in the sense of “a system of methods”) that embraces tools (aka “automation”) but emphasizes the role of skilled technical personnel who guide and drive the process.
The essence of this methodology lies in its humanism (we foster responsibility and resilience by putting the methodology under the control of each practitioner), its ontology (how we organize and define the various priorities, ideas, activities, and other elements of testing), and its heuristics (fallible methods of solving a problem). In RST, we’re not afraid of learning, applying, and discussing words like “ontology” or “heuristics”. For us, words are important tools we use to help us develop our expertise and to describe and explain our work.
Rather than being a set of templates and rules, RST is a mindset and a skill set. It is a way to understand testing; it is a set of things a tester knows how to do; and it includes approaches to effective leadership in testing.
What We Mean By Rapid
What Are the Foundations of RST?
The Evolution of RST
What the Methodology Is Compatible With
That’s a start. There’s much more to learn about RST.