Product
Continuous QA Engineer
Continuous QA Engineer
Start with Public app URL; optional priority journeys. Later scheduled cycles revisit accessible sources and saved cases. Coverage depends on the available sources and runtime. Tests and measurements require actual execution evidence; unavailable capabilities remain visible as coverage gaps.
- 1/wkEvidence reports
FactoriesStart with your sources
IdleIllustrative runWalking critical flows onapp.example.com
src/server/cart/summary.ts
- Flows walked
- 0
- Draft pull requests
- 0
Draft pull requestfix/checkout-summary-no-discount into your default branch
Fix checkout summary for carts with no discount
Related solutions
See how teams in this category put agents to work.
Integrations
0 integrationsGet started with Continuous QA Engineer
Pick an example, connect your tools, and review the first run.
Set up the Continuous QA Engineer agent template for this project. Follow /SKILL.md for the exact CLI commands.
Goal: Explore accessible flows after changes, reproduce failures, and retain regression cases. Return evidence and repair recommendations; add tested patches when source is available.
1. Install the CLI if it is not on PATH, check that I am signed in, and select my team and project.
2. List the first-party workflow templates. If `continuous-qa-engineer` is listed, instantiate it with `--path.slug continuous-qa-engineer` and start the run; otherwise create a project from this template at /new?template=continuous-qa-engineer&preset=trial.
3. Share the run id, follow the run until it finishes, and summarize its outputs and changes.
Ask me before spending FTAI or changing anything outside this repository.
Launch from Claude Code, Codex, Cursor, and other agents.