Use this checklist before recording or running web tests in Ranorex Studio. It helps you avoid common setup issues such as browser prompts, blocked automation, unstable profiles, and incorrect endpoint configuration.
Before you start
Choose your execution type, decide how you plan to run your web tests:
- Local browser execution: Run tests directly against a supported browser installed on the run machine.
- WebDriver endpoint execution (Grid/cloud): Record/create the web test locally, then run it against a WebDriver endpoint configuration (capabilities) on a Selenium Grid or cloud provider.
Note: Web tests still have to be recorded locally (even if you’ll execute them remotely).
Best practices for setup
Use a clean browser profile
For stable testing, use a clean browser profile (or a dedicated test user/profile) not used for daily browsing. This helps avoid:
- first-run tours / welcome dialogs
- sign-in prompts and saved sessions
- cached state
- interfering extensions
Confirm Ranorex browser automation add-on is enabled (for recording/local runs)
For recording and local execution, make sure the Ranorex automation add-on/extension is enabled in the target browser.
Control browser updates in team environments
If browser auto-updates are enabled, web tests can break unexpectedly (especially on CI agents). For shared machines and build agents, consider:
- pinning browser versions, or
- scheduling updates and validating tests after updates
Keep the environment stable
- Use consistent screen resolution and OS scaling
- Keep system language/locale consistent across machines where possible
- Avoid running other UI automation tools that may interfere with the browser