S8 · 2–4 weeks
Verification Harness Build
Build a verification harness that generates demanding cases, compares behaviour and uses deliberate faults to prove the tests can fail.
Constructed handover specimen · not a client finding
A deliberate fault tests the test
- Trigger
- Would the harness notice if an access check stopped enforcing organisation boundaries?
- What you receive
- A controlled mutation removes the boundary in the test environment. The harness attempts the cross-organisation operation and must reject the mutated build.
- Decision supported
- If the suite stays green, the result is a coverage defect. The retained finding says which invariant escaped and what evidence closes it.
Who it is for
Products where ordinary example-based tests cannot expose enough of the failure surface.
- The work
- We build an in-repository harness that generates demanding cases, compares behaviour, inserts deliberate faults to grade the tests and leaves a repeatable coverage process with the team.
- The boundary
- The harness strengthens product-specific verification. It does not replace security testing, specialist assurance or human decisions about the product’s intended behaviour.
What you receive
A repository-integrated harness, measured coverage baseline and target, findings ledger and repeatable operating playbook.
- Duration
- 2–4 weeks
- Price (GBP)
- £18,000
- Commercial shape
- fixed