v2.1.99

Installation

• Download plugin (3MB ZIP file) from here below
• In IntelliJ, go to Settings -> Plugins. Click on the "gear" icon and Install plugin from disk.

Special Release

For teams that need Java 11 and Karate <= 1.4.1 support.

Note that only debugging a Karate feature file directly run from the editor will work. Hybrid debugging where Java / JUnit is the entry point will not work for Karate feature file breakpoints.

v2.1.3.EAP

Installation

• Download plugin (3MB ZIP file) from here below
• In IntelliJ, go to Settings -> Plugins. Click on the "gear" icon and Install plugin from disk.

Fixes OpenAPI / Swagger import for unusual JSON content types

v2.1.2.EAP

Installation

• Download plugin (3MB ZIP file) from here below
• In IntelliJ, go to Settings -> Plugins. Click on the "gear" icon and Install plugin from disk.

Fixes issues with debugging Gradle projects when debug session was initiated from Java.

Running Tests via IntelliJ (not Gradle)

For Karate debug support to work, the native IntelliJ Java run configuration should be used. But in Gradle projects, running a JUnit test uses a different kind of run configuration by default. You can change this behavior in Settings > Build, Execution, Deployment > Build Tools > Gradle > Build and run

Set the Run tests using option to Choose per test as shown below.

Now, when you right-click on the JUnit class (or method) and debug (or run), you can choose to use the "native" IntelliJ Java runner as shown below:

Now, a debug session started from the Java or JUnit entry point will also stop at breakpoints in Karate feature files. If you need to set custom VM options, those are easy to do in the Java or JUnit run configuration.

v2.0.7.EAP

Installation

• Download plugin (3MB ZIP file) from here below
• In IntelliJ, go to Settings -> Plugins. Click on the "gear" icon and Install plugin from disk.

Open API support

To convert an OAS or Swagger file to a "spec" file that makes it easy to create a Karate mock, right click on the file and use the "Karate Import" menu as shown below:

 

You need a PRO license. Refer to this example for more details and practical usage: https://github.com/ptrthomas/karate-oas-demo

History

45 - 2024-05-20 - First Version
46 - 2024-05-21 - Absorb fatal errors and add comments to generated spec js file

Debug Build (file ends with 9999.zip)

2024-06-13 - disables reference scanning of java classes and karate features
2024-06-27 - disables java module scanning during a debug session, and reduces cache usage by the debug process
2024-06-28 - support Karate 1.2 (run only) and stepping into features from module libraries (JAR files)

v2.0.0.EAP

Refer to instructions: V2 Refactor 2024

If you already downloaded a version, look at the last number in the filename (or the file upload date) to see if a newer version is available.

Version History
2024-03-11 | 37 - JS line before gherkin comment no longer flagged as error
2024-02-29 | 34 - fix JS += and binary operand formatting, ternary expression syntax
2024-02-23 | 31 - fix JS indenting
2024-02-22 | 30 - fix formatting issues
2024-02-21 | 25 - Console error links to feature, fixed set syntax, module working directory for run config, improved structure view, syntax errors don't affect other steps
2024-02-20 | 23 - Fix run-config TextArea look / behavior, JSON re-formatting intentions (quick-fixes)
2024-02-19 | 22 - JSON indenting works within doc-string sections, support JVM parameters in run config
2024-02-14 | 21 - Fixed file-icon visibility in light mode, Java.type() and read() can navigate to reference
2024-02-08 | 20 - Fixed eval keyword and JS loop syntax, license encoding changed (re-login required)
2024-02-05 | 19 - Support old versions of IntelliJ starting from 2021.1, Code Formatting works
2024-02-01 | 16 - First Early Access version