Risikobasiert explorativ testen

Risk-Based Exploratory Testing

Automated checks verify what we already thought to script; exploratory testing (James Bach, Elisabeth Hendrickson, Michael Bolton) combines learning, test design, and execution to uncover the failure modes nobody anticipated.

Workflow

1. Prioritize test charters by risk and blast radius:
   • Never attempt to test every theoretical permutation blindly. Rank test focus by:
     • User & business impact: Core task completion, data loss/corruption risk, permission boundaries, financial/quota accuracy.
     • Change surface & complexity: Newly modified modules, complex state machines, async coordination, and areas with prior bug history.
2. Formulate concise exploratory charters:
   • Structure each investigation around:
     • Explore: [target feature, workflow, or component]
     • With: [specific inputs, role personas, timing/network conditions, or state variations]
     • To discover: [potential failure modes, state inconsistencies, or usability traps]
   • Example charter: "Explore task creation -> agent launch -> mid-run cancellation -> restart -> result view using different workspace roles, malformed inputs, and an interrupted connection."
3. Apply falsification thinking (Feynman):
   • Ask at each step: "What input, sequence, or timing would prove my assumption that this works is wrong?"
   • Follow anomalies immediately: when a response is slightly slow, a toast flickers, or a counter looks off by one, pivot the charter to probe that seam.
4. Keep test data realistic and isolated:
   • Use realistic domain data (multi-word strings, Unicode/accents, realistic file sizes, multi-item histories) inside isolated test workspaces without touching production records or live third-party side effects.
5. Know when to stop and what to automate:
   • Conclude exploratory passes once the high-risk charters are covered and diminishing returns set in.
   • Recommend high-value, recurring checks for permanent automated test coverage.