Services Quality assurance & conformance
Quality assurance & conformance
Quality assurance, conformance testing, automated tests, and code review — manual and automated. If a tool can see the defect, it is on the merge path. No tool left unused.
What it is
Quality assurance is the merge path: conformance suites, automated tests, and code review that can actually stop a ship. Manual review is for architecture, invariants, and the cases no analyzer can name. Automated review is CodeChecker, clang-tidy, clangsa, and Coverity-class cleanup on every check-in — not a quarterly scan.
Conformance testing proves interoperability (IPv4/IPv6, ARP, IGMP/MLD, API contracts) instead of hoping the lab notebook was right. Unit, integration, property, and hermetic protocol tests run in CI. KLEE and Z3 sit on the same path when the defect is a proof. The same analyzers run on CI images and workstations so the toolchain is a gate, not tribal knowledge.
No tool left unused: if it is in the toolchain, it is a gate. A paid analyzer that never fails the build is a decoration. We inventory what you already own, turn it on, and add the tests and human review the tools cannot replace.
Who it is for
Platform, protocol, and product teams that need a measurable quality program — not a dashboard and a hope that review happens.
Capabilities
- Quality assurance programs with measurable merge and release gates
- Protocol and API conformance testing (IPv4/IPv6, ARP, IGMP/MLD, contracts)
- Automated unit, integration, property, and hermetic protocol tests
- Manual code review for architecture, invariants, and tool-blind spots
- Automated code review: CodeChecker, clang-tidy, clangsa, Coverity-class cleanup
- KLEE, Z3, and theorem-shaped gates where the defect is a proof
- Parallel test infrastructure and TET-class harnesses
- The same analyzers on CI images and workstations — CodeChecker, clang-tidy, clangsa, KLEE, Z3, TET
How we engage
- Inventory tools already paid for, tests that never run, and reviews that never block the merge
- Put human review and every applicable analyzer on the same path — no tool left unused
- Make conformance and automated tests CI, not a lab ritual
- Leave a runbook and a red build that means something
How we work
Scope the failure modes
What must never break, what can degrade, and what the audit trail needs to prove.
Build or harden
Implement with OTP supervision, tests, and measurable gates — or review and repair existing systems.
Ship with proof
CI packages, demos, and runbooks so the next engineer can own the system without archaeology.
Engage
Ready to scope this engagement?
Tell us the system, the constraints, and the failure modes that matter.