Test automation readiness review
For product teams with working software but uneven automated coverage—especially before a major version or when manual regression has become a bottleneck.
Who it is for
Engineering leads at B2B or internal products between roughly eight and forty contributors, often running mixed stacks (web APIs, background jobs, mobile clients). You already have some tests; you need a grounded plan rather than a framework migration pitch.
What you receive
- Written report (typically 25–40 pages) covering suite health, layering, data strategy, and CI runtime
- Risk-ranked backlog of test additions and repairs with effort bands
- Annotated examples: two tests we refactor or add in your repo (with your review)
- 90-minute recorded readout for engineering and product stakeholders
- Two weeks of email clarifications after delivery
Explicitly excluded
- Full rewrite of your application under test
- 24/7 on-call for production incidents
- Procurement or licensing of commercial test tools on your behalf
Provider & process
Led by a senior consultant from Grid Harbor, paired with your designated engineer for repository access. We follow the engagement path: kickoff, deep dive, draft findings, revision, handover.
Duration & delivery
Four calendar weeks from signed scope and access. Remote-first with optional on-site day in Gqeberha for kickoff or readout (travel billed at cost if outside Eastern Cape).
Preparation
Read-only repo access, CI history export (last 30 days), list of top five business flows, and named contact for defect triage meetings.
Pricing basis
Fixed fee quoted after a 45-minute scope call; see rates for typical bands. A 40% deposit confirms the start date.