FRT (Cucumber/Gherkin)
Write functional regression tests in plain language and let VisualQ generate, execute, and report on the underlying Playwright code.
VisualQ FRT lets product managers, QA engineers, and developers describe user
journeys in Gherkin (Given/When/Then), then automatically:
- Generates the underlying Playwright TypeScript code with AI.
- Executes the test on the managed VisualQ worker (Chromium / Firefox / WebKit).
- Records a step-by-step timeline with screenshots, traces, video, and HAR.
- Lets you push the results to Xray Cloud or share them as a public living document.
Why VisualQ FRT vs. classic Cucumber
| Classic Cucumber + Xray | VisualQ FRT | |
|---|---|---|
Write .feature files | ✓ | ✓ |
| Maintain step definitions | Manual, in your repo | Auto-generated by AI, reviewable |
| CI / browsers / waiting | DIY (GitHub Actions, Playwright, fixtures…) | Managed worker with Playwright trace + video |
| Reporting | cucumber.json, screenshots, manual | Step timeline, side-by-side reruns, signed asset URLs |
| Living documentation | None / manual export | Public living-doc URL (opt-in) |
| Quality pillars (a11y, perf, VRT) | Separate tools | First-class Then steps (Then the page should pass accessibility (axe) with score >= 90) |
Architecture at a glance
[Editor] → /api/frt/compile (AI → Playwright)
↘
[Run] → /api/frt/run → Worker (Playwright) → /api/worker/callback
↗
[Reporting] ← Firestore (frt_runs) + S3 (screenshots / traces / video)