karate-testinglisted
Install: claude install-skill testland/qa
# karate-testing
## Overview
Karate authors HTTP API tests as Gherkin-flavored `.feature` files with
`Given / When / Then` steps, but unlike Cucumber the steps are **executable
directly** - no glue code is required ([karate-readme][readme],
[karate-docs][docs]).
[readme]: https://github.com/karatelabs/karate
[docs]: https://docs.karatelabs.io/
This skill covers the API-testing slice of Karate. Its mock-server and
UI-automation modes are out of scope here.
## When to use
- The team wants feature-file-based authoring (Gherkin shape) without
step-definition glue code (the Cucumber pain point).
- Multi-language test teams: Karate's DSL is approachable for non-
Java developers (the `.feature` file IS the test; no Java to read).
- API + mock + perf in one tool - Karate's distinguishing feature is
cross-mode reuse of feature files.
- Teams that need built-in JSON path + schema-fuzzy matching with
one keyword (`match`).
If the team is already deep in REST Assured fluency, evaluate
`restassured-testing`. For
non-JVM stacks, use `postman-collections`
or `tavern-testing`.
## Install
Maven (consult [karate-docs][docs] for the current version - Karate
publishes regularly under group `io.karatelabs`, artifacts
`karate-core` and `karate-junit5`):
```xml
<dependency>
<groupId>io.karatelabs</groupId>
<artifactId>karate-junit5</artifactId>
<version>${karate.version}</version>
<scope>test</scope>
</dependency>
```
Pin `${karate.version}` to a specific release