Release notes v1.5.0


Another release of Ranorex Webtestit is out!

We know you’ve missed us.

We’re back after our vacation season with the new release that brings many fresh features and improvements, as well as bug fixes.

Again, many of these improvements and fixes are the result of your valuable feedback, so we would like to thank you all! :slight_smile:
As always, the whole Ranorex Webtestit team is waiting for your feedback.

Here’s what’s new in Ranorex Webtestit version 1.5.0:


  • Element Drag and Drop Workflow updates - As you already know, creating your test steps can’t be easier than this - Use Ranorex Selocity to send the desired element selector directly to Ranorex Webtestit, drag the generated element to the code and pick an action from the list to generate actions. And if you are new to Ranorex Webtestit, we have added some useful comments in the Page Object files that will guide you through the whole process of creating the test steps, and updated the comments in our Test files to make the whole process even more clear and simple :slight_smile: So before you dive in creating your awesome automated tests with Ranorex Webtestit, make sure to read our guiding comments first!

    Additionally, we updated the default generic names for newly created methods with more meaningful ones, so that you always know what are you currently dealing with, and what your methods are about. The names consist of the actual element name and the selected actions or steps, so if you are performing a click on a, let’s say, the home button of your web page, the generated method will be called clickHomeButton().


  • Credentials Management
    As you are already familiar, Ranorex Webetstit supports various third-party service integrations like Jira, TestRail, and SauceLabs. Of course, the mentioned services require you to have an account which you need to connect, and for storing your personal data Ranorex Webtestit uses your Operating System’s keychain to store the credentials if you check the Remember password checkbox. You can find more about credentials storage in this dedicated post.

  • Edit element selector from code - You may come across a situation where the selector for your previously created element has changed and needs to be updated. This is most likely to happen if you are dealing with dynamic elements. Luckily, there is a simple solution for this. Using our element panel, you have the possibility to update the actual selector, by clicking the Edit with Ranorex Selocity button. With this feature implemented, we introduced the same possibility to edit the element selector directly from the code editor, using the context menu. In order to achieve this, you need to have an active connection with Ranorex Selocity. Update the selector with Ranorex Selocity, send it back to Ranorex Webtestit and you are back on tracks.


  • Downloading dependencies for test execution - With this feature, maven dependencies for test execution are downloaded and installed in the background upon opening the project, so that you no longer need to wait on this process when running your first test.

  • Test run indicator animation
    When you are ready to execute your test and hit the Run test button, our cool Rocket animation is launched indicating the start of the process. However, Ranorex Webtestit first checks and, if needed, downloads the newest WebDrivers, cleans the project and installs the required dependencies as a “prepare phase“ of the whole process. In this situation, some users may not have noticed that the test run has actually started, so we have updated our animation to indicate that the execution has started as soon as things are in the motion starting with the mentioned “prepare phase”.

  • Ranorex Selocity menu entry - Ranorex Webtestit works best with our free Chrome extension Ranorex Selocity. Use this extension to generate robust selectors and send them directly to the application. We have added a dedicated menu entry for Ranorex Selocity where you can find all the information needed to get started using this awesome extension.


  • TestRail integration dialog updates - We update the TestRail integration dialog with a Start free trial link. So, if you haven’t used TestRail before, we encourage you to hit the link, create your trial account and explore the benefits of this service. Also, you will notice the “Where are my credentials being stored” link, which points out to an article where you can find out everything about how Ranorex Webtestit stores your credentials and personal data.

    Bug fixes:

  • Report not visible - Fixed the test report not being displayed when the report panel is maximized

  • Headers overlapping Status bar - Fixed the Panel headers overlapping the status in some layout combinations

  • TestRail import - Performing the TestRail import caused some unnecessary settings to be stored

  • Endpoints file visibility - Setting the default.endpoints.json file not to be displayed in the project tree (using the projectTreeFilter
    Property in the Webtestit.json file) resulted in the file also not being displayed in the execution panel

  • WindowsOS Custom endpoint issue - Desired Capabilities in the Custom endpoint dialog did not properly escape the key values

  • Keyboard shortcuts - Eclipse keyset -The CTRL+D shortcut was used for the action “Delete current line” but at the same time also for “Select next occurrence” (duplicate default shortcut)

  • Symlink folder - The project tree used to crash and stay empty if your project contained a directory symlink. Now these are ignored

    Existing limitations with OperaDriver:
    As we previously informed you, a mismatch between the OperaDriver and Opera version 62 resulted in tests not running in Ranorex Webtestit.Meanwhile, a new version of the OperaDriver has been released to support the latest version of Opera, however, this version introduced another bug, i.e. OperaDriver is not starting at all right now.
    This means that the tests still won’t run in Ranorex Webtestit until Opera solves the issue with their driver.
    You can uncheck the local Opera endpoints in the Execution Panel for now and re-enable them when the issue is fixed. You can also follow the discussion regarding current OperaDriver issue on GitHub.

You should receive the new version automatically via the auto-updater once you restart the app.
Alternatively, you can download the version here