Release notes v1.8.0


Another release of Ranorex Webtestit is out!

Good news everyone!
With this release, we tweaked our tool a bit more, fixed some annoying bugs, and introduced some new features so that Ranorex Webtestit runs smoother than ever. Special thanks go out to our users who reported the bugs and helped to make our tool even more awesome by providing us with their constructive feedback :sunglasses:
Check out our list of those new features and bug fixes included in this release.
As always, the whole Ranorex Webtestit team is waiting for your feedback.


  • Python data-driven sample project - As you already know, you can download and explore our samples for Java, TypeScript and Python projects. For all our Python fans out there, we added a data-driven Python project which uses the data-driven testing best practices. Make sure to download it under the Sample project category, or clone it as a remote project.

    If you want to find out more about how to get started with Python, check out our medium blog post, or our official User guide.

  • Preferences dialog updates
    We updated our cool preferences dialog with two new fields under the Project settings category - Always excluded and Project tree filter. This way you can easily exclude files from being shown in the project tree. Always excluded files will also be hidden when Show all files is toggled.

    We have also added a show/hide password button in all the password fields.

Bug fixes:

  • Python screenshot on failure - As you already know, Python was implemented with our previous release, and is in a preview mode. In Python projects, after a failed test run, the report did not display the generated screenshot on failure. This issue is now fixed.

  • Project creation dialog - In some cases when the project creation dialog is not focused, and the user clicks few times around, the prerequisites and requirement warning is discarded allowing project creation despite important dependencies missing.

  • Report stack trace - clicking on the link in the expanded stack trace of a failed report does not jump to the test file at the relevant code line

  • Java projects - running a test without a presence of a page object file shows a not so useful error stack trace. The error description is now updated

  • Log panel improvements - Fixed the issue where clicking on the settings icon in the log panel toolbar, and then clicking on the code caused parts of code to be marked, and added an icon placeholder in the settings dialog.

  • Ranorex Selocity edit selector - Ranorex Selocity did not update the selector correctly if the selector sent from to the Ranorex Webtestit was renamed inside the app and when “Edit with Ranorex Selocity” option was activated.

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