Product

Mobile Website QA Engineer

Start with Website URL. 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.

Start with Start with your sources Try the demo

1/wkEvidence reports

FactoriesStart with your sources

IdleIllustrative run

Walking 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

Integrations

0 integrations

Get started with Mobile Website QA Engineer

Pick an example, connect your tools, and review the first run.

Use template Try the demo

Set up the Mobile Website QA Engineer agent template for this project. Follow /SKILL.md for the exact CLI commands. Goal: Investigate navigation, inputs, overlays, and responsive layouts across mobile viewports. Deliver screenshots, reproducible failures, and targeted repair guidance. 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 `mobile-website-qa-engineer` is listed, instantiate it with `--path.slug mobile-website-qa-engineer` and start the run; otherwise create a project from this template at /new?template=mobile-website-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.

Related solutions

Integrations

Get started with Mobile Website QA Engineer