JourneyMesh

Open-source journey validation

Validate cross-service journeys as users experience them.

JourneyMesh executes mapped user journeys against real applications and service instances. It verifies that expected states, transitions, and outcomes can actually be reached—and records evidence for every step.

Working prototype · Federated Nextcloud file sharing
UJG bindingPlaywright adapterAppium adapterNextcloud driverKeyboard + touch profilesWeb + Android accessibility observers

Services can be healthy while the journey is broken.

Infrastructure checks confirm that services are running. JourneyMesh checks that people can complete the cross-service workflow those services are intended to provide.

Services onlineJourney unverified

One execution path, composed from independent layers.

JourneyMesh translates a journey description into a common execution plan, then combines it with an automation adapter, application driver, interaction profile, and optional evidence observers.

6
6 layers — from journey intent to runtime evidenceBuild the execution from interchangeable parts.

Alice shares a file with Bob across two Nextcloud instances.

Alice uses the Nextcloud A web interface to offer a file to Bob as a remote recipient. Switch Bob’s lane between the successful Nextcloud B browser and Android executions to compare their paths and evidence.

Federated file sharing

Last run passed
2actors
2instances
2profiles
1journey
Open full journey map

Full journey map

Both actors, service instances, phases, steps, states, and transitions in one view.

See what happened at every step.

Select any state or transition above to inspect its expectation, runtime result, chosen input modality, resolved application surface, and attached evidence.

State assertionsTransition resultsExpected effectsSelected input modalityScreenshots and tracesAccessibility findingsSource-model references
i

Browser and Android accessibility findings support journey analysis but do not establish WCAG conformance. Native findings are hierarchy heuristics; they do not assess TalkBack behaviour and require manual review.

Choose the execution you want to validate.

Run Alice and Bob entirely in browsers, or run Alice in a browser and Bob in the Android app. Each YAML test records its own journey evidence and report.

browser-sharing
pnpm exec journey-mesh test examples/nextcloud-filesharing/mesh.yaml --test browser-sharing
native-recipient-sharing
pnpm exec journey-mesh test examples/nextcloud-filesharing/mesh.yaml --test native-recipient-sharing

Make the journey part of deployment validation.

JourneyMesh connects mapped intent to real execution, helping maintainers verify that distributed workflows continue to work across versions, configurations, service instances, and interaction profiles.