v1.4.1

First, a big THANK YOU to all new contributors !

New Contributors

• @​kang-mansher made their first contribution in karatelabs/karate#2315
• @​MohabMohie made their first contribution in karatelabs/karate#2318
• @​lucarota made their first contribution in karatelabs/karate#2325
• @​dvargas46 made their first contribution in karatelabs/karate#2343
• @​barathraju-43 made their first contribution in karatelabs/karate#2354
• @​dersvenhesse made their first contribution in karatelabs/karate#2368
• @​dovikos made their first contribution in karatelabs/karate#2370
• @​byd-android-2017 made their first contribution in karatelabs/karate#2375
• @​GeorgeLBS1 made their first contribution in karatelabs/karate#2376
• @​tstanczak made their first contribution in karatelabs/karate#2392
• @​luanapassis made their first contribution in karatelabs/karate#2400
• @​ksola made their first contribution in karatelabs/karate#2409
• @​bharath2203 made their first contribution in karatelabs/karate#2415

For those interested in participating in Hacktoberfest, you can find instructions here: Karate and Hacktoberfest

Fix List

Some notable improvements:

• UI testing - driver.intercept() (Chrome only) now returns a mock, which opens up some advanced use-cases, see #2361
• some teams reported a slow down in Karate 1.4.0 especially when a lot of JS re-use was involved, which should be fixed, see #2329

Here 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 each defaults to fail if array is empty

You 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 = true

if a match each fails 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 a match each, it would always return an empty array, and the match would always pass.

Docker image now in karatelabs organization

Until 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-debugserver dependency. 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