Web testing in Ranorex Studio lets you automate websites and web apps with a workflow that’s very similar to desktop testing: record actions, build a repository, add validations, and run the test to get a report.
Web UI can be highly dynamic (changing attributes, nested frames, client-side rendering). The next articles cover the key differences and best practices that make web tests stable and maintainable.
Supported browsers
Ranorex Studio supports the following browsers for test automation:
- Microsoft Internet Explorer
- Microsoft Edge (Chromium-based)
- Microsoft Edge (Legacy)
- Mozilla Firefox
- Google Chrome
- Chromium
Ranorex Studio uses browser plug-ins to enable automation in supported browsers.
Note: Need to test additional browser/platform combinations (for example, remote browsers, grids, or cloud providers)? Use Selenium WebDriver integration.
Web testing overview
Web testing and desktop testing in Ranorex Studio are very similar. The basic web testing process in Ranorex Studio is as follows:
Note: Websites can have highly complex structures. This is why it may sometimes be a good idea or even necessary to extend the above process by manually tweaking the recorded test with additional code. We’ll cover this in the later subchapters.
Recommended knowledge
Before you start, it helps to understand basic web concepts (DOM, frames/iframes, dynamic content) and these Ranorex Studio areas:
Ranorex Studio fundamentals
The Ranorex Studio Fundamentals cover the core building blocks (actions, repositories, reporting) you’ll use in every web test.
Ranorex Studio advanced and expert
For web testing, we recommend being comfortable with:
- Ranorex Spy (UI identification and repository structure)
- RanoreXPath (robust element location strategies)
- Code modules and the user code library (optional but useful for advanced scenarios)
Next steps
If you’re new to web testing in Ranorex, follow this order: