-
Notifications
You must be signed in to change notification settings - Fork 6
Changelog
Peter Thomas edited this page Jan 28, 2024
·
1 revision
- Update to final IntelliJ IDE platform 2023.3
- No longer using JetBrains Marketplace for license purchase
- Introduced PLUS subscription level in addition to PRO
- To run tests you require at least a PLUS subscription
- Update to final IntelliJ IDE platform 2023.2
- Support running Karate addons, starting with Kafka support
- Exception about invalid text ranges related to incomplete multiline string literals.
- Properly set working directory and environment variables with 2023.2.
- Parsing and highlighting of .feature files was causing UI freezes for some incomplete
matchexpressions.
- Support JetBrains IDEs 2023.2
- Parsing of
matchexpressions with nested pairs of()or[]on the left-hand-side expression.
- Support
contains only deep. - The Karate test runner is now properly working when executed with the debugger. Previously, the error
Test framework quit unexpectedlywas shown. - The debugger tool window is now properly activated when a breakpoint is hit in a Karate file.
- Newly created Karate run configuration now use
$MODULE_WORKING_DIR$as the default working directory (#31).
- Show a notification when the Karate debugger is launched without a valid license for the Karate plugin.
- Fixed bugs in Postman import, import errors will no longer stop the import, but will be added to the generated feature file as comments.
- New action "Import with Karate" to convert files into Karate's .feature file format. Supported file types are Postman, Postman JavaScript, HAR, OpenAPI, Swagger, cURL. The action is available in the context menu of the project view and in the tools menu.
- New intention "Format JSON" to reformat injected JSON content.
- New intention "Simplify JSON" to simplify and reformat injected JSON content.
- New intention "To Multi-Line" to turn a plain JSON literal into a multi-line JSON
- New intention "To Single-Line" to turn a multi-line JSON literal into single-line JSON
- Formatting a .feature file now also formats injected content, e.g. JSON inside a .feature file.
- JavaScript highlighting values passed to
* url .... - JavaScript highlighting values passed to
* path .... - JavaScript highlighting values passed to
* param .... - JavaScript highlighting values passed to
* method .... - Highlighting of invalid HTTP method names passed to
* method .... - Support for 2023.1 EAP
- Folding of multiline strings.
- Exception executing quick fix "Create Examples Section".
- Allow to use the "Shorten Classpath" settings for Karate run configurations.
- Compatibility with 2022.3.
- Update bundled Karate JAR to version 1.3.0
- #18: JsonPath shortcut form expressions marked as syntax errors
-
#19:
NullPointerExceptionduring debugging. - Exception using breakpoints with a Karate 1.3 preview release.
- Now basic features are free and can be used without a license.
-
#14: Highlight JSON on the right-hand-side value of
jsonsteps as JSON. -
#14: Highlight XML on the right-hand-side value of
xmlsteps as XML.
- New action "Hot Reload" to allow refreshing the current
.featurefile in a debug session.
- Moved action "Step back" into the left debugger toolbar and updated the icon.
- Evaluation of expressions in the Karate debugger. It's now possible to evaluate complete steps, e.g.
def myVar = value, and simple variables likemyVar.
- Support for
get expressionandget[0] expressioninsidedefexpressions.
- Support for JavaScript expressions on the left-hand-side of
matchexpressions, e.g.* match [a, b] contains value. - Better names for run configurations, which reference a
Scenario:orScenario Outline:without description. - Support for JSON-Path exressions on the left-hand-side of
matchexpressions.
- #6: Running a Scenario Outline from the gutter results in the entire feature file being run
- #7: agged scenarios are terminated if run from the gutter
- #8: Feature descriptions are tossing errors if certain characters/keywords are included
- #10: XPath/jsonPath appears to be causing problems with the "match" keyword
- #11: XML declarations are generating errors when included in multi-line doc strings
- #12: karate.filterKeys() is sometimes preventing the next Scenario from being executable from the gutter
- Support for the
karateobject and references to built-in JavaScript.
- Debug support (including "step back" and Karate + Java mixed-mode)
- Support the
requestkeyword - Support the
configurekeyword - Show a test console view for Karate run configurations
- Support multiline strings with the
evalkeyword - Don't show error
Expecting newline or semicolonfor function declarations inside injected JavaScript expressions
- First public release of the Karate plugin on the JetBrains marketplace
- Forked the JetBrains Gherkin plugin
- Added test coverage for lexer and parser using all Karate demo files
- New lexer with support for Karate's syntax extensions
- Added support for
defandtextdeclarations - Highlighting of XML, XPath, JSON5, JsonPath, JavaScript for right-hand-side values of
defdeclarations. - Support the
evalkeywords and implicit JS expression whenevalwas omitted. - Support the
matchexpression - Support code completion of support keywords in steps
- Warn about required whitespace around
=in a def statement, e.g.* def myVariable=value - Support completion and references to the global
karateobject in injected JavaScript code - Run configurations to execute Karate .feature files with the bundled Karate JAR file.
- Search for Karate in the project's classpath when executing a .feature file
- Editing of content injected into multiline strings