Website QA & Troubleshooting

Run webpage checks with replay evidence

Execute webpage actions and assertions from a checklist, output a machine-readable report, and use Recording to retain evidence for Replay during regression testing and failure analysis.

Example · run webpage checks and review persistent Replay evidence

Integration options

Prerequisite:
Fetch and fully execute the official Lexmount Setup Prompt returned by https://browser.lexmount.cn/api/agent-setup/browser-cli.
Continue only after installation, authentication, and environment validation all pass; otherwise stop and report the failure truthfully.

Task:
Use browser-cli only to create one temporary Lexmount Cloud Browser Session, check the navigation flow from https://rust-lang.org/ to https://rust-lang.org/learn/, and save a structured report in artifacts/web-check-report.json.

Execution:
1. Open the website and confirm that the document title contains "Rust" and the main heading is "Rust."
2. Click the visible "Learn" link, confirm that the final pathname is /learn/, then verify that the document title and main heading contain "Learn Rust."
3. Perform every action and assertion in order. Determine page state from the URL, document title, or visible elements without using a fixed sleep.
4. After the first failure, mark all remaining steps as skipped and retain every result collected so far.
5. Verify the JSON report, close the Session, and retain its Replay.

Acceptance:
All webpage checks must pass, the JSON report must be non-empty and parseable, and the Session must close successfully. The generated JSON must be available as a clickable file in the final Codex response. If the main task succeeds but cleanup fails, report partial success.

Cleanup:
On success, failure, timeout, or cancellation, close only the Session created by this task and retain its Replay. Never close a pre-existing Session.

Return:
Report only the status, check count, first failed step, report path, Replay retention, cleanup result, and sanitized error summary, then provide the generated JSON report as the final item. Do not expose API keys, Project IDs, Session IDs, Replay IDs, connect URLs, or WebSocket URLs.

Integration options

Prerequisite:
Fetch and fully execute the official Lexmount Setup Prompt returned by https://browser.lexmount.cn/api/agent-setup/browser-cli.
Continue only after installation, authentication, and environment validation all pass; otherwise stop and report the failure truthfully.

Task:
Use browser-cli only to create one temporary Lexmount Cloud Browser Session, check the navigation flow from https://rust-lang.org/ to https://rust-lang.org/learn/, and save a structured report in artifacts/web-check-report.json.

Execution:
1. Open the website and confirm that the document title contains "Rust" and the main heading is "Rust."
2. Click the visible "Learn" link, confirm that the final pathname is /learn/, then verify that the document title and main heading contain "Learn Rust."
3. Perform every action and assertion in order. Determine page state from the URL, document title, or visible elements without using a fixed sleep.
4. After the first failure, mark all remaining steps as skipped and retain every result collected so far.
5. Verify the JSON report, close the Session, and retain its Replay.

Acceptance:
All webpage checks must pass, the JSON report must be non-empty and parseable, and the Session must close successfully. The generated JSON must be available as a clickable file in the final Codex response. If the main task succeeds but cleanup fails, report partial success.

Cleanup:
On success, failure, timeout, or cancellation, close only the Session created by this task and retain its Replay. Never close a pre-existing Session.

Return:
Report only the status, check count, first failed step, report path, Replay retention, cleanup result, and sanitized error summary, then provide the generated JSON report as the final item. Do not expose API keys, Project IDs, Session IDs, Replay IDs, connect URLs, or WebSocket URLs.