This solution is easy to teach to people without a lot of coding experience, but it is capable of being extended by those with a deeper skillset. Because Karate also uses Scenarios in Feature files, teams who are using a Cucumber framework can create Karate tests which live alongside legacy Cucumber tests, enabling a team to increase productivity by developing tests which are faster and more stable, while continuing to run their legacy tests. Both tests can exist side-by-side, in the same repository, so the team doesn't have to switch all at once. As Cucumber tests are rewritten in Karate, tags can be adjusted to coordinate which tests are run by which framework.

Karate is an excellent solution for API testing and works well for UI testing as well. I have used it with both Selenium and Playwright for browser automation. It has an extensive set of features with lots of useful capabilities built-in. When more advanced, custom capabilities are needed, the built-in functionality can be augmented using Java and/or JavaScript. We can easily make use of any available Java library and we can manipulate Java objects while debugging in a way which is not typical when working with Java. New code can be written and executed at runtime, while debugging, which makes for very quick development in a very productive, interactive workflow. The framework is very well documented.

There are some aspects of working with Karate that take some getting used to. For instance, it is a bit odd at first for one scenario to call another scenario as if it were a function, but once you learn how it works, it is easy to work with.

I can't recommend Karate enough. It's really transformed the way my organization tackles API projects, and enabled our QA engineers to focus more on what they do best -- ensure quality in our products -- and less on learning to become Java developers.

Karate is well documented and well supported. [sensitive content hidden] is all over Stack Overflow, so if you run into an issue, chances are he's already answered your question, or will have an answer for you within hours. But the DSL is so simple to learn, chances are you won't have any issues getting up and running with it. And unlike other solutions, Karate offers a full range of automation capabilities: client-side assertions for API, UI & desktop testing, server-side mocks/simulators, and even performance testing (executed by Gatling).

This is hard to answer, as Karate's Java interop capabilities make calling Java code incredibly easy, which means if Karate doesn't offer something "out of the box," you can simply spin up a custom Java class that accomplishes what you need it to. That said, it would be nice if Karate offered some built-in Kafka capabilities (e.g. the ability to write to and read from a specified topic using a REST endpoint).

It is great, I've implemented it in 3 different companies already. It allows me to start covering my API with tests right away and in a fast pace

Ease of setup, ease of writing tests even for juniors and the fact that it uses Gherkin, allows everyone to understand the tests.

Visual testing still need some improvement, Karate is strong for API and performance tests

Until now, very good, I only had a problem with the logs and my CI tool, but in general it is a good tool to automate API tests

It is easy to understand and the executions are quick and clean

The price of the product, I know that the product needs a revenue to keep working, but the price can make that other testers may prefer using cheaper options

Very satisfied. It has made my automation work very efficient.

It is an excellent tool in all sense. Used it for both API and UI automation. Found pretty amazing with parallel execution, negligible flakiness, code less automation.

Gatling is not yet up to the mark as much as Jmeter.