An order fails somewhere across three services

Orders, products and invoices are separate services. When the journey breaks, everyone looks at their own logs.

Why ordinary tests miss it

Each service has its own tests, and they pass. The journey crosses all three, so a change in one breaks it without any single team seeing it.

Add each service’s repository to the project.
On the environment, give each repository its own address under Services. Each step goes to the service whose code defines its endpoint.
Describe the journey once. It crosses the services the way your users do.
Monitor it, and send the alert to the channel all teams read.

Run log on Acceptance

An example of what you see, in Journey Lanes’ own words. The numbers and names are made up.

Each step went to the service whose code defines it, so the failing step points at one service and one team, with the request and the answer.

Connect a repository, describe the journey, and run it against the mock in a few minutes.