Functional testing
Design tests that find defects, not tests that reassure.
01 — The problem
Your regression campaigns take several days and find very little. The test cases were written three years ago, nobody dares delete them, and nobody knows any more which ones cover what. When an incident hits production, the question “why didn’t this test case exist?” has no answer.
02 — What we do
- 01
Rebuild coverage from risk
We start again from business flows and their criticality, not from the history of test cases. Many cases disappear; the ones that remain have a reason to exist.
- 02
Apply design techniques, not intuition
Equivalence partitioning, boundary values, decision tables, state transitions. These techniques find defects that ad hoc test writing does not.
- 03
Introduce exploratory testing methodically
Chartered sessions, time-boxed, with a written debrief. Exploratory testing is not testing without preparation: it is testing without a script, which is very different.
- 04
Shrink the regression campaign
Selection based on the impact of the change rather than on exhaustiveness. A shorter, better-targeted campaign protects better.
- 05
Make acceptance testing tool-ready
Acceptance criteria written to be verifiable, and therefore automatable later without rewriting.
04 — What you receive
Named deliverables, not promises. You know what you will receive before we start.
Risk-based coverage map
Cleaned-up test case repository
Including what was removed, and why.
Exploratory session charters
Regression test selection strategy
05 — Technical ecosystem
Tools do not make quality. We master them so that we can choose the right one, not to use them as a selling point.
- Xray
- TestRail
- Zephyr
- Cucumber
- Gherkin
- Jira