Playwright smoke & journeys
T0 browser journeys and smoke checks on public templates.
Warning
Creytix Playwright smoke & journeys is in active development — here's what it will do and what's live so far.
Overview
Rule checks like Protect can tell you a page's metadata is right without ever loading the page in a browser. Playwright smoke & journeys is meant to close that gap — running real browser checks against public templates so you catch what only shows up when a page actually renders and someone, or something, clicks through it.
How it works
The target flow: a defined journey — load the homepage, open a product page, submit a form — runs in a real browser against your public templates, and Inspector reports whether the journey completed cleanly or hit a broken step.
Steps
- •
Define a journey
Describe the flow that matters — a page load, a click-through, a form submission.
- •
Run it against your public templates
The journey executes in a real browser, not a simulated DOM check.
- •
Get a pass/fail per step
See exactly which step in the journey succeeded or broke.
- •
Feed results into the CI gate
Wire journey results into the CI gate alongside Protect's rule checks.
Capabilities
- Browser-level checks — real page loads and interactions, not static analysis.
- Journey-based testing — flows defined as a sequence of steps, not a single-page snapshot.
- Target: CI gate integration — journey results feeding the same pre-ship gate as Protect.
Limits & honest scope
Playwright smoke & journeys is actively being built. Today:
- Journey coverage is limited to a narrow set of public templates, not your whole site.
- Full CI gate integration alongside Protect is the target, not yet the default wiring.
- Treat this page as the direction this tool is headed. Check the changelog for what's actually running today.