Pull request testing

Review the journey, too.

Pair code review with an E2E check of the preview environment. Connect AuraCheck through your CI workflow and attach the resulting evidence to your review.

Preview environment testingTargeted smoke suitesReviewable run outcomes
Web seller-settings testREAL RUN / GIF
Full report
01 / THE WORKFLOW

Give the change somewhere to run.

Deploy a preview, wait for readiness, and select the test cases affected by the change. Make the preview URL reachable from the runner.

02 / THE EVIDENCE

Make the check an explicit CI step.

Use the run API with a scoped token and wait for a terminal result. Configure your own merge gate in the source-control platform; AuraCheck is not an automatic GitHub App installation.

A FEW GOOD QUESTIONS

Clarity before
you commit.

Talk to the team
How does AuraCheck run an E2E test?

You define the user journey and expected outcomes. AuraCheck uses vision AI to interact with the interface, execute the steps, and attach evidence to the run. Review the generated cases before execution, then inspect the results and screenshots.

Do I need to write test code?

You can start from a PRD or plain-language steps. The generated cases and automation scripts stay reviewable, so QA engineers can refine assertions, data, and execution details when needed.

Can I test web and mobile apps?

Yes. AuraCheck supports browser, Android, and iOS testing. The Windows and macOS desktop app runs Android tests on a connected device or emulator. iOS connects through WebDriverAgent and requires its own host and device setup.

READY WHEN YOU ARE

Your next release deserves proof.

Bring one important user journey. See what AuraCheck can do with it.