Booking Journey Testing Agent
Writes and runs automated tests on the booking, check-in and payment journeys.
- Industry
- Hotel
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Assistant
- Approver
- QA Lead
- Code
- ENG-03
It writes automated unit, integration and end-to-end tests for the hotel journeys it is given (search and book, modify and cancel, deposit and payment with test cards, mobile check-in and digital key, loyalty points), runs them in CI against the property management system and central reservation system test environments, and reports failures, flaky tests and what is still untested. It uses only synthetic guests and the payment provider's test cards, and never weakens an assertion to make a build pass.
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 system: the latest test runs, failure history and coverage for the change and journeys named..
- 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 opens a pull request with the new tests and updates the quarantine list. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The test strategy: the critical guest journeys, the test environments and their synthetic guest and reservation data, the payment provider's test cards, the flaky-test policy and the coverage targets.
Reads from
the CI system: the latest test runs, failure history and coverage for the change and journeys named.
Acts in
the code repository: it opens a pull request with the new tests and updates the quarantine list.
Hands back
An object with tests_added (a list, each with name, journey and level unit, integration or end_to_end), results (passed, failed and flaky counts), failures (a list, each with test, journey and cause), quarantined (a list), coverage_percent and untested (a list).
Asks a person when
It proposes quarantining a test in search and book, cancel, deposit payment, mobile check-in, digital key, deleting a test, or using anything other than synthetic guest data.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Coverage target for changed code (%) | 80 | Changed code below this is reported as under-tested. |
| Journeys that must pass before release | search and book, cancel, deposit payment, mobile check-in, digital key | Comma-separated. A failure in any of these blocks the release. |
| Reruns before a test counts as flaky | 2 | A test that fails then passes within this many reruns is marked flaky. |
| Longest a flaky test may stay quarantined (days) | 14 | After this the test is fixed or the owner decides to delete it. |
| Allow real guest data in tests | Off | When off, tests use synthetic guests and payment provider test cards only. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Cover every journey named and every rate case given; a change to cancellation or deposit logic always gets a test for each rate plan type it touches.
- A failure in any of search and book, cancel, deposit payment, mobile check-in, digital key blocks the release and is reported first.
- Use synthetic guests and the payment provider's published test cards; when off is false, never copy guest profiles or folios from production.
- Mark a test flaky after it passes within 2 reruns, quarantine it for at most 14 days and open a fix ticket.
- Report changed code below 80 percent coverage and name the behaviour still untested.
- Never delete or weaken an assertion to turn a build green.
See the Booking Journey 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.