Releases: karatelabs/karate
v1.2.0
Highlights
A "final" release after half a year. Multiple fixes and stability improvements. Thanks to all who tested RC releases.
For what's fixed in this version, refer to this list.
Note that we have an experimental NPM package for Node / JS teams. Please spread the word !
Breaking Changes from 1.1.0
Please read the 1.2.0 Upgrade Guide. The good news is that this will not impact most projects.
Karate also starts tracking a very basic level of analytics. Read more here.
New Contributors
Thanks to all contributors, past and present !
- @lyxell made their first contribution in #1728
- @gerben86 made their first contribution in #1734
- @heyspearsy made their first contribution in #1744
- @treyturner made their first contribution in #1750
- @gillius made their first contribution in #1787
- @packleader made their first contribution in #1796
- @FanYuliang made their first contribution in #1829
- @Fresh-D101 made their first contribution in #1841
- @OreOreDa made their first contribution in #1884
- @ismail-s made their first contribution in #1891
- @bipin-k made their first contribution in #1897
- @borzykin made their first contribution in #1965
- @bischoffdev made their first contribution in #1998
Full Changelog: v1.1.0...v1.2.0
Artifacts Released
- Maven artifacts
- Standalone JAR (download below)
- ZIP Release (download below)
- Karate-Robot JAR (download below)
- Docker Image
Contributors
Assets 5
v1.2.0.RC6
ℹ️ This is planned to be the last RC release for version 1.2.0. Please test and provide feedback !
We want to make sure that our new release automation pipeline delivers artifacts that work for all Java versions (8 and above).
For what's fixed in this version, look at the issues here that have the fixed tag.
This release includes the Docker image.
Note that we have an experimental NPM package for Node / JS teams. Please spread the word !
Breaking Changes from 1.1.0
Please read the 1.2.0 Upgrade Guide. The good news is that this will not impact most projects.
Artifacts Released
- Maven artifacts
- Standalone JAR (download below)
- ZIP Release (download below)
- Karate-Robot JAR (download below)
- Docker Image
v1.2.0.RC1
This release is for the benefit of those blocked by some specific issues.
For what's fixed in this version, look at the issues here that have the fixed tag. A screen-shot of the 7 issues is shown below for handy reference.
- Maven artifacts
- Standalone JAR (download below)
- ZIP Release (download below)
- Karate-Robot JAR (download below)
Note that the Docker container has not been released.
v1.1.0
No Breaking Changes
Yes really.
Highlights
- fixed: improve memory usage especially for "called" features #1685
- fixed: some nagging issues with concurrent threads and
karate.callSingle()andcallonce#1558 - the
@ignoretag is now "baked-in", and there are some new ones, refer to the docs - and you can "bind" tags to the value of
karate.envin a very interesting and useful way, refer to the docs - if you use the karate-gatling integration, please scan through the improvements in #1622
Artifacts
- Maven artifacts
- Standalone JAR (download below)
- ZIP Release (download below)
- Karate-Robot JAR (download below)
- Docker image (for Chrome and Distributed test execution)
Contributors
You are all awesome 🙏
@jfougere #1679
@ericdriggs #1666 #1672
@sormuras #1646
@dhamo-pk #1629
@aaronjwhiteside #1624 #1625
@abhi-rao #1611 #1613
@brianngo313 #1599
@BurhanH #1594
@arthur25000 #1584 #1590
@chaudharydeepak #1581
@dinesh19aug #1573 #1585
@ivangsa #1570
@joelpramos #1562 #1603 #1615 #1636 #1637
@babusekaran #1550
@aleruz #1534 #1556
@parched #1529
@workwithprashant #1524
What's Fixed
For a list of all issues closed in this release, go here.
Stay Updated
To keep track of news and releases, follow us on Twitter @KarateDSL or on LinkedIn or by joining this group.
Contributors
Assets 5
v1.1.0.RC5
This is a Release Candidate for teams to try the version which is "in development" - and identify potential issues or un-intended breaks in functionality.
There are no breaking changes !
Please look at the last 1.1.0.RC3 release for details on what to expect.
There are many small improvements. The highlight of this release is a focus on performance and reduced memory usage.
- Maven artifacts
- Standalone JAR (download below)
- ZIP Release (download below)
- Karate-Robot JAR (download below)
Note that the Docker container has not been released.
To see a list of issues that should be fixed in this version, look at the issues here that have the fixed tag.
v1.1.0.RC4
This is a Release Candidate for teams to try the version which is "in development" - and identify potential issues or un-intended breaks in functionality.
There are no breaking changes !
Please look at the last 1.1.0.RC3 release for details on what to expect.
We've been trying to fix a particular bug related to the use of karate.callSingle() and mixing Java code - so this release is mainly for that set of users.
- Maven artifacts
- Standalone JAR (download below)
- ZIP Release (download below)
- Karate-Robot JAR (download below)
Note that the Docker container has not been released.
To see a list of issues that should be fixed in this version, look at the issues here that have the fixed tag.
v1.1.0.RC3
This is a Release Candidate for teams to try the version which is "in development" - and identify potential issues or un-intended breaks in functionality.
There are no breaking changes !
One significant change is that the @ignore tag is now "built-in". We decided this made sense after observing 4 years of Karate usage. What this means is that you no-longer need to pass ~@ignore on the command-line or test-runners, it has become a "baked-in" convention.
Take a moment to review all the "magic" tags in Karate. There are just a few. And note the brand-new tags @env and @envnot they can be really useful when you switch environments a lot. They can "bind" or "un-bind" some tests to some environments. You can find the docs here.
In the last release we considered making a breaking change to the path keyword. We got a lot of feedback and realized a lot of teams used the pattern we were trying to change. Thanks to everyone who provided feedback and proposed alternatives and it helped a lot ! We have a better solution in place.
Perf Testing Improvements
If you use karate-gatling take some time to read this thread. We've tried to make it easier to re-use existing test-suites as performance-tests by avoiding some configuration or conditional logic you needed to take care of previously. Please do test these improvements out, they can make a big difference - and we need the feedback !
- Maven artifacts
- Standalone JAR (download below)
- ZIP Release (download below)
- Karate-Robot JAR (download below)
Note that the Docker container has not been released.
To see a list of issues that should be fixed in this version, look at the issues here that have the fixed tag.
v1.1.0.RC2
This is a Release Candidate for teams to try the version which is "in development" - and identify potential issues or un-intended breaks in functionality.
Breaking Changes
The path keyword will encode the / character. You do not need to ever include the / character. Always build path-strings by using the comma-delimited form of path. Please change your tests to never use the / character on the right side of the path keyword.
Before:
* path 'foo/bar/' + someVariableAfter:
* path 'foo', 'bar', someVariableAs a convenience, if you have a lot of tests in the old, no-longer-supported form, you can use path raw to fall-back to the old behavior. But we recommend that you switch to the recommended path form above to avoid breaking your tests again in the future.
The rationale is that Karate will apply URL-encoding to the path for all cases, including the / character. For a detailed discussion, see #1561. Note that url can be always used if you want to force a specific string, and no URL-encoding will be performed in that case.
- Maven artifacts
- Standalone JAR (download below)
- ZIP Release (download below)
- Karate-Robot JAR (download below)
Note that the Docker container has not been released.
To see a list of issues that should be fixed in this version, look at the issues here that have the fixed tag.
v1.1.0.RC1
This is a Release Candidate for teams to try the version which is "in development" - and identify potential issues or un-intended breaks in functionality.
- Maven artifacts
- Standalone JAR (download below)
- ZIP Release (download below)
- Karate-Robot JAR (download below)
Note that the Docker container has not been released.
To see a list of issues that should be fixed in this version, go here.
v1.0.1
Bug Fix Release
This fixes a few major bugs in version 1.0.0 (that was released only 3 weeks ago) that only a small proportion of teams would run into. But it is recommended that you upgrade. Those who use karate.callSingle() should definitely upgrade. Thanks to all those who helped troubleshoot and help us fix these.
The details of the 9 issues closed can be found here.
Those migrating from versions of Karate less than 1.0 - should refer to the upgrade guide.