Projects
A swimlane for every role in the product
Journey Lanes reads a repository on GitHub, GitLab, or Bitbucket, or an OpenAPI document, and draws the journey as a swimlane with one lane per role. It builds a mock backend from that code, runs the flow against it, and keeps monitoring the path.
What it does
You describe the journey in plain language, for example: a company admin logs in and creates a user, then an employee logs in and orders a product. Journey Lanes turns that into a flow with one lane per role.
The flow runs against a mock backend built from your code, or against a live environment. It can run again after every deploy and on an interval, with an alert when a step fails.
Besides GitHub, GitLab, and Bitbucket repositories, it reads OpenAPI, GraphQL, and gRPC definitions.
Who it is for
Product teams that want to test user journeys end to end. Anyone on the team can build and change a flow without writing test code.
Status
Live at journeylanes.com, where you can create an account.
Who built it
A product of Developer Lab.
Planned next
- Load-test a whole flow, with many virtual users walking every step, not a single step.
- Sign in with a GitHub App or OAuth, instead of a pasted token.
- Company sign-in through Keycloak, next to the built-in accounts.
- An audit log of who changed what.
- Edit the graph on the canvas: add a step and connect it by hand.
- Alert escalation and quiet hours when a step keeps failing.
- A light theme.
From the roadmap in the Journey Lanes repository. No dates are attached.