CI and exports
Run flows after every deploy, and take them with you
Deploy checks fit into the pipeline you have. Exports turn a flow into test code your team can keep in its own repository.
Deploy checks
Choose the flows an environment runs after a deploy, and create its hook. The hook has its own token per environment, shown once and stored as a hash, so your pipeline needs no user account. Each call starts a deploy check: the flows run one after another, a failure alerts the project’s channels, and the first pass after a failure says it recovered. Deploy runs count towards the plan’s flow runs.
curl -fsS -X POST https://flow.developerlab.nl/api/hooks/deploy \
-H "Authorization: Bearer fch_…" \
-H "Content-Type: application/json" \
-d '{"revision":"<commit sha>","repo":"owner/name"}'
- The reply has a status URL to poll, also as Markdown for a job summary, so a GitHub Actions step can fail the job when the flows fail.
- With a repository and a full commit sha, Journey Lanes sets a GitHub commit status per environment, using the project’s GitHub token (which needs commit statuses: write).
- Argo CD’s notification controller can call the hook once per synced revision; that is set up in your Argo CD, nothing in your application changes.
Exports
A flow’s overview has Export, made from the flow’s graph alone, so no credential, token or run value can end up in a file:
- Playwright: a
@playwright/testfile using therequestfixture, with checks as assertions. - Postman: a v2.1 collection with variables for references and tests for checks.
- Flow file: a versioned JSON file with the graph and mock settings, which imports again.
In Playwright and Postman, roles sign in with the OAuth password grant from variables, or take a token directly; generated bodies and email steps are marked for you to fill in.
Import
Flows → Import flow makes a new flow from a flow file, after checking its shape. Roles that match the project’s own take their ids, so your environments’ test accounts apply. Monitoring stays off on an imported flow.
API
The deploy hook is the interface meant for automation. The rest of the API is the web app’s own and isn’t offered as a public API yet.
Check your next deploy
Create a deploy hook for your test environment and call it from your pipeline.