-
Notifications
You must be signed in to change notification settings - Fork 0
Tutorial Spec to Test
Turn a markdown acceptance-criteria spec into running Playwright tests.
Deep: Tutorial 02 · Test Authoring.
Include a ## Acceptance Criteria section (bullets become requirements):
# Products page
## Acceptance Criteria
- Navigate to /products
- Page shows heading "Products"
- Schedule Demo button is visibleExample in-repo: prompts/examples/vm-create.md.
zyvor-qa generate --spec path/to/feature.md
cat tests/fixtures/requirements.json # parser output
ls tests/generated/- No LLM → rule-based / template generation
- With
LLM_PROVIDER+ key → freer prose + richer TypeScript (quality gate falls back to Jinja if LLM output is bad)
zyvor-qa run --source local --spec path/to/feature.md
open reports/qa-summary.htmlExit code is non-zero on failure (CI-safe).
Move stable specs from tests/generated/ → tests/manual/ so they always run with zyvor-qa test.
Natural Language Tests · GitHub Integration · Notifications and Reports
Start: Home · Getting Started · Tutorials · Workflows · Admin · Dashboard
Tutorials: Spec→Test · NL · GitHub · Coverage · Visual · Notify · External CI · Agent CI · zyvor.dev · Specs
Build: Architecture · Config · Authoring · Structure · Multi-browser · Rust
Actions: Mission Control · Journeys · API/Auth · Probes · Schedules · Ask Zyvor · Autofix
Ship: API · Webhooks · Security · CI/CD · Deploy · Releases · Enterprise
More: Troubleshoot · FAQ · Glossary · Contributing · Demos · Docs
Guides