Rapid Software Testing fosters what you must have to test well: a love of testing.
By this, we don’t mean the love of paperwork and button-pushing. Instead, we’re talking about learning, analyzing, finding trouble, and helping people. That’s the heart of testing. That’s what Rapid Software Testing (RST) focuses on.
How do you do great testing?
- How do you get excited about testing?
- How do you sustain that excitement?
- How do you use that energy to help people become better testers?
- How do you foster respect for the testing process?
- How do you cultivate the kind of testing that is worthy of respect?
RST answers these questions.
It is a way of doing, teaching, and talking about testing that gives responsible people the freedom and the tools to do testing well. Whether you are a tester, a developer, a manager, or anyone else for whom testing matters, RST gives you a lot to love about testing.
If you want to adopt RST for yourself, you don’t need anyone’s permission or coordination. That’s a personal matter.
But if you want a team or a whole company to adopt RST, that’s going to require patient, persistent leadership.
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.