Release notes v1.6.0


#1

Another release of Ranorex Webtestit is out!

We’re happy to announce the latest release of Ranorex Webtestit that brings some exciting feature updates to make your text execution workflow smoother than ever.
There were some annoying bugs in our previous release, but we caught and fixed them all in this release thanks to your feedback and reports.

Here’s what’s new in Ranorex Webtestit 1.6.0:

IDE-Features:

  • TestRail integration updates - Managing your test cases with TestRail and Ranorex Webtestit is a piece of cake: import your test cases from TestRail, execute the tests, export the results back and that’s it! We updated this neat feature and improved the test case import workflow. Now, from the import dialog, you can select and filter out only those test cases that are marked as “automated”.

    testrail1

    After you import the tests, the imported test file contains some additional information about the caseID, suiteID, and a direct link for opening the test case in your browser. If there are test steps available, they will be formatted and shown in the test file as comments.
    When exporting the results back to TestRail, the test run is now formatted so that it contains information about the browser and endpoint, time and date of the test run, and information about the Operating system on which the run was executed. After the export was competed successfully, you can jump over to your TestRail’s account dashboard and view the results simply by clicking the “View in TestRail dashboard”. This can also be accomplished directly from the generated report of your test run by clicking the “Jump to test case in TestRail button.”

    testrail2

  • Test execution workflow update - The Ranorex Webtestit team is constantly working on improvements, taking the requests of our dear users in consideration. In order to make the test execution snappier, we updated our test run process.
    Previously, Ranorex Webtestit ran a dependency check on every single test run, which ended up more time consuming than we thought. As this check is already executed whenever you open a project or update a project’s dependency files, we removed this phase from each test run, reducing the preparation time for a test run dramatically, while retaining the original functionality 99% of the time :sunglasses:
    Related topic -1433

    If you still get a dependency error, we have made the dependency check available as a manual trigger. You can find it in the F1 command menu (Simply hit the F1 key, type in the “Restore build dependencies”) and also in the applications Run menu (Run -> Restore build dependencies)

  • Test Report updates - After each test run, a test report is generated and stored in the reports folder. The report file contains a short summary of your test run, but also a stack trace information which is visible if the report is expanded. We updated this feature to automatically open and expand the report by default after a test run, so that all the information about the cause of the potential test failure is immediately visible.

    reports

  • Ranorex Selocity extension tips - As you already know, Ranorex Webtestit works best with Ranorex Selocity. Use our free chrome extension to generate robust selectors and send them back to Ranorex Webtestit. For our users who haven’t used this feature yet, we strongly suggest you to do so, it can’t get easier than this. We updated the instruction on how to use this two awesome tools together. Those instructions are available on first project creation dialog, in the dedicated Ranorex Selocity menu, the element panel and the context menu of the chrome browser when the extension is installed, so make sure to read the instructions carefully and benefit from this workflow!

  • Project creation dialog - We enhanced our project creation dialog with a nicer and more visible language indicator, and besides that we added a tooltip explaining the role of the Java project’s root package specification available on mouse over.

Bug fixes:

  • Files not loaded properly - In some cases, selected files are not properly loaded and the content is not shown in the code editor (files shown as empty) - fixed. Related topic - 1430

  • Sauce Labs - When the “remember credentials” option is unchecked, and when stopping a test run, credentials for the Sauce Labs endpoint are prompted, even dough the endpoint is not marked as active for that test run.

  • Empty report generation - In a situation when a compilation error happens, an empty report was generated - fixed. Related topic - 1433

  • New project creation - When creating a new project with Ranorex Webtestit, the indicator that marks the selected project’s programming language and framework was not visible enough.

  • Instantiate Page Object snippet - in TypeScript projects, the Instantiate Page Object snippet default const name was “test”, now changed to “po”

  • Buy now links - The Buy now links on the welcome panel and login dialog lead to Ranorex Webtestit landing page instead of the shop

  • Code lens widget placement - Code lines widget gets misplaced when @Test notation in the test file is moved away from the default position. Related topic - 1301

  • Opera endpoint - due the issues with the previous release of OperaDriver, test execution on Opera endpoint was not available out of the box. With the new OperaDriver released, there are no more issues with running your automated tests on this endpoint

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