Common Workflows

Common Workflows

Operator recipes combining CLI and Mission Control. Customer page map: docs/customer/workflows.md.

Smoke after a deploy

1. zyvor-qa test --grep @smoke (or Mission Control ▶ Smoke)
2. Check reports/ / Findings / QA Runs
3. Optional: Slack/Teams — Notifications and Reports

Spec → tests → report

1. Write markdown AC — Spec to Test
2. zyvor-qa run --source local --spec … or Full pipeline card
3. Optional autofix: ENABLE_AUTOFIX — Autofix and Regression

GitHub backlog → PR comment

1. Label issues qa — GitHub Integration
2. zyvor-qa run --source github --pr-number N
3. Or webhook on pull_request

Expand coverage

1. zyvor-qa discover --source github
2. zyvor-qa run --source github --expand-coverage — Coverage Expansion

Record and replay a journey

1. Flow (--steps / --describe) — Journeys and Flows
2. Import codegen if you recorded in Playwright
3. HAR record/replay for offline network fixtures
4. Public practice: Test zyvor.dev

API, auth, live data

1. Auth & session → save session
2. API contract vs OpenAPI
3. Realtime WS/SSE
4. Reuse session on Flow — API Auth Realtime

Visual confidence

1. Route sweep or visual regression — Visual Regression
2. Compare staging vs prod URLs in Mission Control
3. Core Web Vitals card / zyvor-qa vitals

Continuous monitoring

1. Configure an Action once (audit URL, flow steps, TLS)
2. Schedules panel → interval 5 min – 6 h — Mission Control

Gate in product CI

External CI/CD — Action or docker run + upload reports/.

Related

Tutorials Index · CLI Commands · Getting Started