Flagship service
Test Architecture Review
For engineering leads and staff engineers responsible for release quality in a monolith or service mesh with multiple automated suites.
Outcome
You receive a written test architecture document: current-state map, target layering, recommended owners, sequencing for the next two quarters, and explicit non-goals so the team does not over-automate low-risk corners.
Included
- Read-only access to repositories, CI configuration, and recent failure logs
- Structured interviews with two to four people who merge code or triage failures weekly
- Suite inventory tagged by speed, stability, and business risk
- 90-minute readout with your leads (on-site in Stellenbosch or video)
- 30-day email follow-up for clarifying questions on the roadmap
Excluded
- Writing or rewriting production application code
- Implementing the full remediation plan (available as separate advisory days)
- Penetration testing or formal security certification
Process and timeline
Week 1: Access setup, pipeline tracing, and interviews. Week 2: Draft architecture, internal consistency check, readout, final PDF delivery. Engagements assume a single primary product with up to three deployable services; larger estates are quoted separately.
Delivery
Hybrid: kickoff can be at 71 Dorp Street,Stellenbosch,Western Cape,7600 or remote. Interview blocks and readout fit South Africa business hours by default.
Preparation
Grant CI read access, share your last month of main-branch failures, and nominate interviewees who actually touch failing specs. No special test tooling is required—we adapt to your stack.
Pricing basis
Fixed fee for the standard two-week scope; see rates for current figures. A 40% deposit confirms the calendar slot; remainder due on delivery of the final document.