title = "Exploratory Testing for Financial Workflows"

content = """
Exploratory testing combines learning, test design, and execution in real time.
The tester explores the system without a rigid script, following intuition
and risk. It complements scripted tests by finding issues scripted tests
might miss.

**Session-Based Approach:** We use time-boxed sessions with a charter
(e.g., "explore payment failure handling"). Testers document findings,
risks, and ideas during the session. Debriefs capture insights for
future test design.

**When to Apply:** Exploratory testing is valuable for new features,
complex workflows, and areas with frequent change. It helps uncover
usability issues, edge cases, and integration problems. We schedule
exploratory sessions before major releases.

**Documentation:** Session notes include areas covered, bugs found,
and recommendations. We avoid treating exploratory testing as
"ad hoc" — it is structured, purposeful, and reportable.
"""  # noqa: E501

version = "0.0.1"
