- Industry
- Banking
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- Head of Technology Operations
- Code
- ENG-03
It writes and runs automated tests for the bank's critical journeys (sign-in with step-up authentication, payment to a new payee, card freeze, loan application, statement download) and for interest, fee and end-of-day batch logic, using synthetic customers and accounts. It reports failures, flaky tests and behaviour still untested.
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 CI pipeline: the test results, coverage and history for the change..
- 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 Head of Technology Operations with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the code repository: it commits the new tests and posts the test report on the change. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The test strategy: critical banking journeys, synthetic test-data sets (no production customer data in test), interest and fee calculation test vectors, batch and end-of-day test runs, and quarantine rules for flaky tests.
Reads from
the CI pipeline: the test results, coverage and history for the change.
Acts in
the code repository: it commits the new tests and posts the test report on the change.
Hands back
An object with passed, failed, flaky, coverage_percent, failures (a list with test, error and likely_cause), critical_journeys (a list with journey and result) and untested (a list).
Asks a person when
A critical journey fails, a test needs production data, a quarantine runs past 7 days, or the report recommends releasing with failures.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Coverage target (%) | 85 | For the code in scope. |
| Reruns before flaky | 2 | A test passing only on rerun is flaky. |
| Longest quarantine (days) | 7 | Quarantined tests are fixed or removed by then. |
| Critical journeys | sign-in, step-up authentication, new payee payment, card freeze, loan application, statement download | Journeys that must pass before release. |
| Use production data | Off | When off, only synthetic data is used. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Cover sign-in, step-up authentication, new payee payment, card freeze, loan application, statement download end to end on every release.
- When off is false, use only synthetic customers, accounts and card numbers that fail the Luhn check.
- Test interest and fee logic against the approved test vectors, including leap years, month-ends and rate changes.
- Rerun failing tests 2 times before calling them flaky; quarantine for at most 7 days.
- Report coverage against 85 percent and list untested behaviour.
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.