« Changelog History


Karate v0.9.2 Release Notes

Release Date: 2019-03-25 // about 5 years ago

  • 🛠 Important Fixes

    🚀 This is a bug-fix release and there are no breaking changes from 0.9.1 (unless you use the Gatling integration, see below) which was released 2 months ago. The main reasons why you should upgrade are the following:

    🔊 Dynamic Scenario Outlines miss some HTML logs #660

    🌲 Only if you use Dynamic Scenario Outlines - the HTTP / console log was being missed for some scenarios in the HTML / JSON report.

    ✅ Some failures in test execution hang Parallel Runner #667

    Some kinds of catastrophic failures especially in the karate-config.js bootstrap - would cause the parallel runner to hang indefinitely.

    🔀 JUnit runner syncs console output better to IDE / IntelliJ #690

    💻 In IntelliJ - clicking on the nodes in the IDE UI for JUnit would not show the corresponding section of console output.

    Gatling integration now works on Java 9 and above #647

    ⬆️ We upgraded the Gatling version we target to 3.X which means we are no longer limited to only Java 8. You need to upgrade the Gatling Maven plugin version, and depending on which Gatling features you have used - there may be API changes. Refer to this Github diff for details.

    👍 WebSocket Sub-Protocol Support #662

    ➕ Added support for the sub-protocol part of the spec.

    💻 Karate UI log TextArea broken #659

    💻 Only if you use the Karate UI - the area in the UI where the log was supposed to collect was not working.

    💻 UI Automation Improvements

    💻 Also we improved the experimental UI automation API, with new driver.switchTo() and driver.value(set) operations.

    🛠 For the complete list of fixes, go here.