Product
Cross-Browser QA Engineer
Cross-Browser QA Engineer
Start with Website URL + browser choices. 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 Cross-Browser QA Engineer
Pick an example, connect your tools, and review the first run.
Set up the Cross-Browser QA Engineer agent template for this project. Follow /SKILL.md for the exact CLI commands.
Goal: Run the same journeys across browsers, isolate behavioral differences, and retain minimal reproduction cases and evidence of corrected behavior.
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 `cross-browser-qa-engineer` is listed, instantiate it with `--path.slug cross-browser-qa-engineer` and start the run; otherwise create a project from this template at /new?template=cross-browser-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.