While competing in the exacting modern software market, many companies find integrating automated testing into their overall testing process beneficial. This guide will help you better understand the different types of automated test solutions and how developers...
Let me kick this blog post off by saying thank you to all of you who have made the Ranorex 7.0 Webinar such a great success. It was a pleasure presenting the highlights of our latest software update, and I have received a lot of valuable questions. As I did not get to address all of them during the webinar, I’d like to take this opportunity and answer the most popular questions in this blog post.
- Can the JUnit compatible report be integrated in Jenkins or other CI tools?
- How does the new WPF plug-in work with 3rd party controls and other technologies?
- Can you convert an existing object repository with WPF items to the new WPF paths?
- Can we execute Selenium tests written in Java or only those written in C#?
- Can you switch endpoints programmatically?
- Can I reuse my existing Ranorex tests, which I have created entirely in code without using the object repository and run them on endpoints?
- Can I perform cross-platform web tests using the same test case in Ranorex 7.0?
- Are you supporting Selenium Grid or cloud providers such as SauceLabs and BrowserStack?
- What about the support of Microsoft Edge?
- Is there any difference to recording web tests in previous Ranorex versions? Do I have to re-record my tests through the WebDriver?
- What is the difference between this Selenium WebDriver integration and Ranorex Remote?
- Which Selenium server versions are supported?
- What are the system requirements to execute Ranorex tests and which environments are supported by the Selenium WebDriver integration?
- Which license do I need to execute a Ranorex test on a Selenium WebDriver endpoint?
Can the JUnit compatible report be integrated in Jenkins or other CI tools?
The JUnit framework is widely accepted and natively supported by most CI environments, such as Jenkins, TFS and Bamboo. Please read this blog post to find out how you can integrate Ranorex automated testing into Jenkins.
How does the new WPF plug-in work with 3rd party controls and other technologies?
The WPF plug-in in Ranorex 7.0 was designed to provide out-of-the-box support for major 3rd party controls, such as Telerik, DevExpress and Infragistics. Even mixed technology modes like WPF controls embedded in WinForm hosts and vice versa, are supported and can be identified completely configuration-free.
Can you convert an existing object repository with WPF items to the new WPF paths?
RanoreXPaths generated by the WPF technology plug-in in Ranorex 7.0 are much leaner and, therefore, not compatible with those generated in previous versions. If you want to convert your object repository to the improved WPF plug-in, you will have to re-identify your controls. We strongly advise you against mixing repository elements created with different WPF technology plug-in versions, as this will cause your test runs to fail.
WPF tests created with a previous Ranorex version will continue to work in the exact same way as they did before. Ranorex 7.0 scans your object repositories for items representing WPF elements. If existing repository items representing WPF elements are found, the legacy mode will be automatically activated for your solution.
For more information about the new WPF plug-in, and to find answers to frequently asked questions about the changes to this plug-in, please refer to this site: Ranorex 7 WPF Plug-In FAQ.
Can we execute Selenium tests written in Java or only those written in C#?
Ranorex is a .NET API for test automation and, therefore, Java test development is not supported. However, if you have existing Selenium tests written in Java, you can integrate them in your Ranorex test report. Head over to our blog “How to Use Ranorex with Existing Selenium Tests” to find out how!
Can you switch endpoints programmatically?
Yes! You can utilize the Ranorex.Host class in order to define the current host at runtime. Ranorex.Host.Local defines the current computer executing your test suite. Defined endpoints can be queried via the Ranorex.Host.AvailableHosts functions. Ranorex.Host.MakeCurrentHost(string name) switches the automation root at runtime and Ranorex.Host.Current returns the currently active automation root. Head over to our API documentation for further details.
Can I reuse my existing Ranorex tests, which I have created entirely in code without using the object repository and run them on endpoints?
Can I perform cross-platform web tests using the same test case in Ranorex 7.0?
Yes, that is not a problem at all. Using the Selenium WebDriver integration, you can run the same web tests across Linux, macOS and Windows now. Simply create endpoints for the platforms you want to run your tests on and then start the same test on these endpoints. Ranorex will do the rest for you.
Are you supporting Selenium Grid or cloud providers such as SauceLabs and BrowserStack?
While there is a general support for grids integrated in Ranorex Studio, we are currently working on tightening the integration with grid providers and latency management in the cloud. You can expect an update on this matter in a future release.
What about the support of Microsoft Edge?
Microsoft Edge is now fully supported again through our Selenium WebDriver integration. Simply use the Open Browser action in the Ranorex Studio action table and run your test on an endpoint where Edge is installed and the Microsoft WebDriver is in place.
Is there any difference to recording web tests in previous Ranorex versions? Do I have to re-record my tests through the WebDriver?
There’s no difference. You have to record web tests using our plugin-based system and can use the new WebDriver integration to replay these tests. You just have to ensure that a test executed on a WebDriver endpoint only contains actions which are supported by Selenium WebDriver.
What is the difference between this Selenium WebDriver integration and Ranorex Remote?
The Selenium WebDriver integration utilizes the WebDriver protocol to retrieve the UI element information of your SUT and processes it locally on your computer. You can use this integration for web tests only. Ranorex Remote executes tests for desktop, web and mobile applications on remote Ranorex Agents. Basically, it is possible to execute a Ranorex test suite on a Ranorex Agent that accesses a WebDriver endpoint. The advantage of using Ranorex Agents is that the test suite is not executed locally on your device anymore, whereas the Selenium WebDriver integration enables you to run web tests on previously inaccessible browsers and platforms.
Which Selenium server versions are supported?
We’ve tested Ranorex on the Selenium server versions 3.0.1 and 3.3.1. Older versions have not been tested, but basically all future versions should be compliant.
What are the system requirements to execute Ranorex tests and which environments are supported by the Selenium WebDriver integration?
You can find a complete list of Ranorex-supported operating systems on our system requirements page. Ranorex tests can access and interact with Selenium WebDriver endpoints on Windows, macOS and Linux environments. Please refer to this site to find out more about the Selenium WebDriver system requirements.
Which license do I need to execute a Ranorex test on a Selenium WebDriver endpoint?
You will need at least a Ranorex Runtime License to execute a Ranorex test on a Selenium WebDriver endpoint. If you would like to learn more about Ranorex licenses and pricing, please refer to our pricing page or contact our sales team.
Automated testing is a crucial part of software development. This guide helps you understand and implement the right types of automated testing for your needs.
Verification and validation in software testing are formal processes of assessing the correctness and completeness of a software product.
APIs and GUIs have different functions and require suitable testing. Ranorex Studio’s test automation gives you the perfect testing program for APIs and GUIs.