From Expo build to release evidence.
Bring a runnable application build into the AuraCheck mobile workflow. Verify the installed experience your users will actually open.
- 01Create a run
- 02Execute the journey
- 03Inspect the evidence
Build first. Test the installed app.
Prepare an installable build for the target device and confirm the app starts successfully. AuraCheck does not replace EAS build orchestration.
Connect the handoff deliberately.
Use your CI process to coordinate the build and local runner. Validate device compatibility and app authentication before adding a release gate.
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.
Your next release deserves proof.
Bring one important user journey. See what AuraCheck can do with it.