Rapid Software Testing (RST)

Overview

Rapid Software Testing (RST) is a human-centered, context-driven methodology that treats the product as a mystery to be investigated. It focuses on people, heuristics, skills, and ethics to find the "bugs that matter" as efficiently as possible.

Part I: Introduction & Core Mindset

• The Product is a Mystery: Do not assume it works; probe it to discover its true nature.
• Testing is Learning: Every test is an episode of learning about the product's status.
• Testing vs. Checking: Testing is a human process of exploration; checking is algorithmic verification. See RST Workflows.
• The Responsible Tester: You are an independent agent accountable for the quality of your investigation.
• Vital Qualities: Empirical, Skilled, Different, Motivated, Available. See Tester Qualities.

Part II: Methodology & Process

1. Model the Product: Use the HTSM to brainstorm coverage.
2. Define Strategy: Use the Test Strategy Guide to prioritize risks.
3. Execute Sessions: Use Session-Based Test Management (SBTM). Use the Session Template.
4. Apply Oracles: Use Oracle Heuristics (FEW HICCUPS) to recognize problematic behavior.
5. Apply Tools: Use tools for checking, but avoid the 13 Automation Traps.
6. Report & Storytell: Use the Reporting Guide and Bug Template (PROOF heuristic).

Part III: Application & Special Topics

• Prospective Testing: Testing ideas and requirements before code exists. Use the Prospective Checklist.
• Signals-Based Testing: Leveraging AI and system signals for deep coverage.
• AI and Testing: Supervizing AI output, transpection, and the productivity paradox.
• Usability Testing: Rapidly assessing user experience and accessibility.
• Adventures in Testability: Advocating for systems that are easier to test.

Part IV: Context & Culture

• Context & Culture: Understanding management, sociology, and how testing looks from the business side.
• The Horizon Scandal: Lessons from a massive systemic failure.

Resources (Assets)

• SBTM Session Template: For focused exploratory sessions.
• Bug Report Template: For professional and actionable bug reporting.
• Prospective Checklist: For meetings and requirements analysis.

Key Examples

Prospective Testing in a Meeting

User: "We're planning a new feature for multi-currency support. Any thoughts?"

1. Refer to Prospective Testing.
2. Use the Cheat Sheet: Ask "What other features will be affected?" or "How will it recover from currency API failures?"
3. Use the Checklist to capture risks.

Supervizing AI Output

User: "The AI generated these 50 test cases for me. Are they good?"

1. Refer to AI and Testing.
2. Perform Transpection: Ask "How do I know these are valid?" and "Are they shallow?"
3. Identify where the AI might be "hallucinating" or providing tautological checks.