Karate is the only open-source tool to combine API test-automation, mocks, performance-testing and even UI automation into a single, unified framework. You don’t have to compile (Java) code. Just write tests in a readable syntax.
Example of automation at GitHub.
Use cases 🥇
Automate API tests. It also supports performance and end-to-end (E2E) tests. Mobile testing is in the roadmap.
Learning curve 🥈
Steep. It’s easy to understand how it works, but it lacks an official step-by-step tutorial where each main DSL keyword is introduced, one at a time. It feels like a framework made by and to “hardcore developers”. The purpose of using Gherkin is to make the tools accessible to non-devs, yet I never felt productive or in control.
The VS Code extension didn’t work at all (e.g. no autocomplete, no debugger, no run test button). In terms of community… there’s not much since it’s a recent tool. The author is an enthusiastic salesperson which led to some bad PR, result of the “my tool is amazing, if you disagree you’re against me” attitude. He’s very active on Stack Overflow and GitHub though, replies within hours!
It’s easier to read than to know what to write. Without autocomplete or good documentation it becomes hard to know how to use the Karate DSL to achieve what you want to do. Your tests use Gherkin’s structure, but you have to mix programming syntax too (e.g. operators, selectors). This sums the downsides of natural (e.g. no refactoring) and programming (e.g. learning curve) languages. The CLI output is very verbose (without colours or whitespace) so it’s hard. The HTML report doesn’t clear results from previous test runs. Oh, and the DSL doesn’t allow inline comments.
You don’t need plugins, since it follows the “batteries included” philosophy. Running tests in parallel is very easy. It includes Mocking, code coverage and HTML reports (but it doesn’t reset results between runs, even when using
--clean, which makes the report useless).
The big difference from Cucumber is that you don’t need to write extra “step definitions” (but you end up mixing Gherkin with programming). You can’t use PageObjects, but you can centralise selectors in a
locators.json to achieve DRY. I could not debug at all, zero of features advertised here worked for me (Cypress, even Selenium, does a better job). On top of that, I got incoherent test results on UI automation.
Documentation is a single README file. It’s verbose, exhaustive for beginners, hard to navigate and find what you are looking for. It feels like the official docs were written by the author but never revised from the perspective of a beginner (e.g. the provided quick start example fails; it can’t be copied because it’s an image; it was faster to skim blogs for examples and reverse-engineer the bits that I needed).
Useful for API testing, because it uses a generic language and can be executed as a standalone. But don’t be fooled, the target audience are developers and it’s not an alternative for UI/E2E tests.