-
Notifications
You must be signed in to change notification settings - Fork 0
CI CD
Hub for shipping Zyvor QA as a gate. Prefer the tutorials below for step-by-step wiring.
| Tutorial | When to use |
|---|---|
| GitHub Integration | Product repo as spec source (issues/docs → generate/run, PR comments, webhooks) |
| External CI/CD | Drop Action/container into any project’s pipeline (GitHub/GitLab/CircleCI/Jenkins/Azure) |
| Agent CI and Kubernetes | This agent’s own smoke/post-deploy Actions + Docker + k8s |
Deep docs: Tutorial 04 · 09 · 15.
- uses: hypersdk/ZyAIQAAgent@v0.4.0
with:
command: test
target-url: https://staging.example.com
grep: '@smoke'Or: docker run … ghcr.io/hypersdk/zyaiqaagent:v0.4.0 test --grep @smoke
Templates: templates/ci/.
ZYVOR_PRODUCT_REPO=owner/repo
zyvor-qa run --source github --spec docs/specs/feature.md --pr-number 42gh api repos/<owner>/<qa-agent-repo>/dispatches -f event_type=staging-deployed- Exit codes — see External CI/CD
-
reports/summary.json— stable CI summary schema - Artifacts:
reports/,test-results/, traces/screenshots
Related: CLI Commands · Deploy and Releases · Configuration.
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