Release notes v1.11.0


Another release of Ranorex Webtestit is out!

It’s no secret that we always cared for our users and their opinions and requests. After a short break made in order to finish up our new workflow requirements we are back with a new release :sunglasses:
In the times like this Ranorex Webtestit brings you some good reasons to keep you busy while making the creation of the automated test suites easier and more effective than ever and al that by takin the request of our users into account.

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.


  • The Debugger
    Finally, it’s there! As many of our dear users requested, we implemented the debugger feature with this release of Ranorex Webtestit.
    Some times, even if we are sure that the tests we wrote are errorless, we encounter the situation where our test scripts are failing and require debugging. If we want to execute our tests line-by-line and verify the output we need help from the debugger. With Ranorex Webtestit this can be achieved using the Diagnostic mode run. Using this feature, you can inspect the test execution line by line, stepping into methods that might cause the code to break, step out of them and resume the execution, and all that by watching the browser performing those actions in real-time :sunglasses:

    The workflow is simple:

    1. Set the breakpoints
      locate the desired code lines in the code editor where you want to place the breakpoints. Along the left margin of the code editor ( as shown on the gif below), you can toggle the breakpoints by clicking on them, or remove all active breakpoints using the “Clear breakpoints” button


    2. Run the test in diagnostic mode! After you are done setting the breakpoints on the specific test steps/code lines, start your debugging session by running the test in diagnostic mode. Do this either by clicking the codelens directly from the code or from the report of your failed test.

    3. Continue, step over, step into…
      Control the test execution and observe the test run using the debugger commands:

      Continue - resumes the test execution process and stops at the next valid breakpoint
      Step over - executes the code line where the breakpoint is set and pauses the execution on the next line.
      Step into - locates and opens the method that is being called when Step into button is clicked and pauses the test execution there.
      Step out - returns to the calling method (steps out of the inspected method after using step into).
      Stop - stops the execution and the diagnostic mode


    With this feature implemented, you can now easily debug your code as you watch the test execution in real-time on your endpoint. So roll up your sleeves, set the breakpoints, start the diagnostic mode and fix those flaky tests!
    Related topics: 967, 1428, 206

  • Ranorex Webtestit Report server

    As we all know, in the software testing process, the reporting part is where it all comes down to, so it is neglectable to talk about the importance of this segment. After the tests have been executed,
    Ranorex Webtestit offers you a report showing all the relevant information about the completed test run. Ranorex Webtestit has a highly modular report, which is made up of handlebar templates, and can easily be customized, like described in this post. What’s new with this feature is that now, you can set up and start Ranorex Webtestit as a report server in the background and easily upload and share the reports with the rest of your team or company. The IP address and the location of the folder where reports will be uploaded can be modified using the server.conf.json file. Also, here you can change the default credentials which are (USERNAME: password).
    The server.conf.json file is located under your .webtestit folder

    Steps to start the server

    1. Open your CMD/Terminal and type in the following command:
      <Webtestit app path> server

    2. The configuration of the report server is stored in the server.conf.json file in your .webtestit folder. If the server is run without the configuration file present, a new one will be created, you will see this message in the terminal output. After this one-time setup is done, and the file is created, you just need to run the report server again.

    3. You can edit the port, username and the password, save the file and your server is ready. If the server is up and running, you should see the following message on your IP: PortNumber URL

    4. Enable the report-server in the Preferences menu
      Check the Enable checkbox, enter the server port (which is 8888 by default and can be edited), provide the credentials (USERNAME: password by default) and hit Connect. Done!

    After you have completed the test run, you will notice the upload report icon in the report panel.
    Click this button and provide your credentials. The link is generated automatically, and all you need to do is to share it with the rest of your team!

Python with Unittest (Preview)

We introduced Python as our third supported programming language together with the Unittest framework. Please note that Python language support is currently in Preview mode, so if you encounter any issues please provide us with your feedback and opinions!

  • PyLint
    Pylint is a tool that checks for errors in Python code, tries to enforce a coding standard and can also look for certain type errors, recommend suggestions about how particular blocks can be refactored and can offer you details about the code’s complexity. PyLint is there to help you write better code. It will also help avoid errors, and things that could not be errors or could be potentially dangerous.
    There are reasons for those squiggly underlines all over your code, and once you know what brings these underlines out, you’ll know what to ignore and what not to :wink:

    Whet starting a Python project the PyLint will be automatically enabled. Follow the lint rules and make your python automated tests even more robust and stable with Ranorex Webtestit.

    If you feel brave and confident enough, this feature can, of course, be disabled so that you don’t see any linter suggestions. To do so, simply open the project settings and under the Language server field, click on the Edit in Webtestit.json button and add the following to the file:

    "languageServer": {
     "python": {
       "plugins": {
          "pylint": {
            "enabled": false
  • Autocomplete functions

    With this feature implemented, we updated the auto-complete methods step for Python-based projects. The methods called are now auto-completed with brackets and parameters.
    Autocomplete helps you complete the names of classes, methods, fields, and keywords. When you invoke code completion, Ranorex Webtestit analyses the context and suggests/offers the autocomplete menu of the available items.
    With code autocomplete you will be able to increase your productivity even more and save your valuable time when writing those rock-solid automated tests.

    Same as the pyLint, this feature can be disabled. To disable the autocomplete feature, enter the following line to Webtestit.json file and set "include_params" to ‘false’:

      "languageServer": {
        "python": {
          "plugins": {
            "jedi_completion": {
              "include_params": false

    For more detailed instructions with screenshots on how to enable or disable certain language server features, hop over to our Python language server settings topic. We prepared this article for you to explain the Python language server features swell as libraries used there.

    Bug fixes:

  • Python projects:

    • Fixed the indentation issue when adding steps to the methods with code broken into multiple lines.
    • Fixed the out-of-sync issue when inheriting from other classes.
  • TestRail integration: “Link Testrail Testcase” feature not showing available TestRail projects on the dropdown menu for a single test sometimes.

  • Codelens - Running a test without an active endpoint was showing wrong dialog information, and is now updated with proper one for adding an Endpoint.

Want to know how to improve your workflow even more and do cross-browser and cross-platform with Ranorex Webtestit and Docker? Check out our new Executing tests on Selenium Grid within docker containers and Dockerizing Ranorex Webtestit articles!

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

Pass capabilities to Sauce Labs executions