UAE · ENBook a demo
Oil & GasEngineeringAssistant

Testing Agent

Writes and runs automated tests.

Testing AgentApplication Engineering
Industry
Oil & Gas
Department
Engineering
Team
Application Engineering
Kind
Assistant
Approver
QA Lead
Code
ENG-03

It writes automated unit, integration and end-to-end tests for operational and commercial applications, covering critical journeys such as raising and closing a permit, recording a gas test, submitting a nomination and authorising a card transaction. It runs them in CI against masked or synthetic data, reports failures and flaky tests, and never weakens an assertion.

How it works

6 steps, and a person signs off before step 6.

  1. 01Looks it up

    Finds the record the request is about in the CI system: test runs and coverage for the change..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  5. 05Asks a person

    Hands the work to QA Lead with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the code repository: it opens a pull request with the new tests and quarantine changes. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The test strategy: critical journeys per app, synthetic well and production data sets, masking rules, the flaky-test policy and coverage targets.

Reads from

the CI system: test runs and coverage for the change.

Acts in

the code repository: it opens a pull request with the new tests and quarantine changes.

Hands back

An object with passed, failed (with reason), flaky, untested_behaviour and coverage_percent.

Asks a person when

A critical-journey test fails, a test would be quarantined, or coverage falls below 80 percent.

ApproverQA Lead

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Coverage target (%)80For changed code.
Reruns before flaky2A test passing on rerun is flaky.
Longest quarantine (days)14Then it is fixed or removed by a person.
Critical journeyspermit raise and close, isolation confirmation, gas test entry, nomination submit, card authorisationComma-separated. Never quarantined.
Use production dataOffOnly synthetic or masked data.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Never quarantine a test on permit raise and close, isolation confirmation, gas test entry, nomination submit, card authorisation.
  • Quarantine flaky tests only after 2 reruns and for at most 14 days.
  • Use only synthetic or masked data when off is off.
  • Never delete or weaken an assertion to pass; aim for 80 percent coverage.

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.

Testing Agent · Oil & Gas | Basinwright Industries