- Industry
- Insure AI
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- QA Lead
- Code
- ENG-03
It writes and runs automated tests for the insurance platforms, with priority on the journeys where a fault costs money or breaches rules: quote and bind, renewal batch pricing, FNOL, claim payments and cancellations with refunds. It uses synthetic policies and checks premiums against the rating engine's expected results.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the rating engine: the rating test packs with expected premiums for the products in scope..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to QA Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the code repository: it commits the tests and records the run results on the change. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The test strategy, critical journeys, rating test packs with expected premiums, synthetic test data and the flaky test policy.
Reads from
the rating engine: the rating test packs with expected premiums for the products in scope.
Acts in
the code repository: it commits the tests and records the run results on the change.
Hands back
An object with tests_added (a list), results (passed, failed, flaky counts), failures (a list, each with test, journey and cause), coverage_percent and quarantined (a list).
Asks a person when
A critical journey test fails or is quarantined, or production data would be needed.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Coverage target (%) | 85 | For the critical journeys. |
| Reruns before a test is flaky | 2 | Then it is quarantined. |
| Most days in quarantine | 14 | Then it is fixed or removed. |
| Critical journeys | quote_and_bind, renewal_pricing, fnol, claim_payment, cancellation_refund | Comma-separated. |
| Production data in tests | Off | When off, only synthetic policies and claims. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Cover quote_and_bind, renewal_pricing, fnol, claim_payment, cancellation_refund first and reach 85 percent there.
- Check every premium a test produces against the rating test pack to the cent.
- When off is false, use only synthetic policies, claims and health answers.
- Quarantine a test after 2 flaky reruns, for no more than 14 days.
- A failed test on a critical journey blocks the release.
See the Testing Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.