Rapid Software Testing (RST)

Overview

Rapid Software Testing 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.

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.
• •The Responsible Tester: You are an independent agent accountable for the quality of your investigation.
• •Tactical Pessimism: Cultivate faith in the existence of trouble.
• •Vital Qualities: Professional testing requires five vital qualities: Empirical, Skilled, Different, Motivated, and Available. See Tester Qualities.

Workflow: The Testing Cycle

1. •Prospective Testing: Test ideas and requirements before code exists. Use the Prospective Checklist and see Prospective Testing.
2. •Model the Product: Use the HTSM to brainstorm what to test.
3. •Define Charters: Create specific missions for testing sessions.
4. •Execute Sessions: Use SBTM to perform focused exploration. Use the Session Template.
5. •Apply Oracles: Use Oracle Heuristics (FEW HICCUPS) to recognize problematic behavior.
6. •Apply Tools: Use tools for checking facts, but avoid the 13 Automation Traps.
7. •Report & Storytell: Use the Reporting Guide and Bug Template (PROOF heuristic).

Detailed Guides

• •Heuristic Test Strategy Model (HTSM): A complete taxonomy for strategy brainstorming.
• •Test Oracles: How to identify bugs (FEW HICCUPS, Blink Oracle, Safety Language).
• •Workflows & Management: Testing vs. Checking, Deep vs. Shallow, SBTM/TBTM.
• •Automation Traps: 13 classic pitfalls when using tools in testing.
• •Prospective Testing: Testing before implementation (The 11-Question Cheat Sheet).
• •AI and Testing: How to supervise AI, transpection, and the productivity paradox.
• •Reporting & Storytelling: PROOF heuristic and Telescoping reports.

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.

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. •Ask: "What other features will be affected?" or "How will it recover from currency API failures?"
3. •Use the Checklist to capture risks.

Avoiding Automation Pitfalls

User: "I want to automate 100% of our UI tests to save time."

1. •Refer to Automation Traps.
2. •Warn about the Maintenance Trap and the Classic GUI Trap.
3. •Suggest the Golden Rule of Tool Adoption to evaluate the true value vs. cost.

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.