Insurance QA is business-rule QA
Every insurance product is a knot of rating rules, state-by-state regulation, product-form variants, and legacy integrations. QA in this space is less about "does the button work" and more about "does this quote match the actuarial spec on this state's form on this effective date."
What we test
Rating Engines
Table-driven regression across every rating factor, state, product form. Property-based testing where it fits.
Policy Admin (PAS)
Guidewire PolicyCenter, Duck Creek Policy, or custom PAS — full quote-bind-issue-endorse-cancel lifecycle.
Claims Workflows
Guidewire ClaimCenter, Duck Creek Claims — FNOL, adjuster workflows, subrogation, salvage.
Billing & Payments
BillingCenter, payment plans, installment schedules, cancellation for non-payment logic.
Portals & Self-Service
Agent portals, customer self-service, mobile FNOL apps. Accessibility included.
Integrations
ISO, LexisNexis, credit bureaus, MVR, telematics providers. Contract + functional.
Techniques that pay off in insurance
- Table-driven tests — one test, N rows, one row per rate factor combination
- Golden-file regression — compare quote outputs to versioned expected values
- State + product-form matrices — auto-generate coverage across the full product footprint
- Time-travel testing — test effective-date logic without waiting for the calendar
Compliance we design around
- State DOI filings — evidence that filed rates match implemented rates
- NAIC Model Audit Rule (MAR) — control-mapped test evidence
- PCI DSS for payment surfaces
- SOC 2 for InsurTech carriers and MGAs
Related
Insurance work is usually a mix of automation + API testing + heavy manual testing on claims and adjuster workflows where automation is uneconomical.