Update dependency com.intuit.karate:karate-junit5 to v1.4.1 #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.4.0->1.4.1Release Notes
karatelabs/karate (com.intuit.karate:karate-junit5)
v1.4.1Compare Source
First, a big THANK YOU to all new contributors !
New Contributors
For those interested in participating in Hacktoberfest, you can find instructions here: Karate and Hacktoberfest
Fix List
Some notable improvements:
driver.intercept()(Chrome only) now returns a mock, which opens up some advanced use-cases, see #2361Here is a complete list of all issues fixed in this release.
Breaking Changes
The good news is that for most teams there should not be any breakages to existing test scripts. But there are a few things to note, read on below.
match eachdefaults to fail if array is emptyYou can read a detailed description in the issue #2364. This may break existing test scripts only if you are extensively using the fuzzy matching short-cut
#[]in enbedded schema validations. The good news is that if you see any of your existing tests break, you can do this to get back the old behavior.* configure matchEachEmptyAllowed = trueif a
match eachfails now with Karate 1.4.1, ensure that any JsonPath expression on the LHS (Left Hand Side) is accurate. The reason for this change in Karate behavior is that previously - if you had an invalid JsonPath expression on the LHS of amatch each, it would always return an empty array, and thematchwould always pass.Docker image now in
karatelabsorganizationUntil now, the karate-chrome Docker image was published at ptrthomas/karate-chrome. It has now moved to karatelabs/karate-chrome.
IDE debugging requires extra dependency
IDE debugging now requires an extra dependency on the classpath. Maven and Gradle users can use the
io.karatelabs:karate-debugserverdependency. For details on how to use the new debug-server in IntelliJ or VS Code, please refer to this wiki page: Debug Server.Experimental Distributed Testing Support Removed
Karate used to have a distributed-testing (experimental) option released in v0.9.5. This is no-longer available as part of karate-core
Heads Up
Karate 1.5.0 will require Java 17. This is a bit sooner than we expected, but reasons are explained in #2401 - mainly because of needing to address some CVEs. 1.4.1 may be the last release that supports Java 11.
Karate 1.5.0 will also change the Maven group-id from
com.intuit.karatetoio.karatelabs. Note that a 1.5.0.RC1 is available for teams to start trying this out. For a smoother transition, the Java APIs would be changed in a future release (most likely 1.6.0).What's Changed
Full Changelog: karatelabs/karate@v1.4.0...v1.4.1
Artifacts Released
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.