OSS Tanbou

combine API tests, mock servers, and performance tests in one Gherkin-style framework

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
8,972
Primary language
Java
License
MIT
Repository last updated
Sep 27, 2026
On this page

Overview

Karate is a test-automation framework that combines API testing, mocking, and performance testing. Its Gherkin-style DSL supports JSON and XML assertions, while v2 is built around Java 21+ and JUnit 6 integration for parallel test execution.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Describe HTTP requests and JSON/XML assertions in a Gherkin-style DSL

Feature and Scenario files can define URLs, requests, HTTP methods, status checks, and response matching so API behavior and assertions remain together.

Sources: [3]

Use the same toolchain for mock servers and performance testing

v2 lists a built-in HTTP mock server and performance testing as core capabilities, allowing functional scenarios to be extended into load-oriented workflows.

Sources: [3]

Best fit

Fits API contract and integration testing that benefits from one shared DSL

It is useful for microservices and external API integrations where functional tests, mocks, and performance scenarios should share a common framework.

Sources: [2][3]

Before adoption

Karate 2.1.3 targets Java 21+ and JUnit 6

The v2.1.3 POM targets Java release 21 and JUnit 6.1.3, and the project publishes a karate-junit6 artifact. Existing v1/JUnit5 projects should review runtime and runner migration.

Sources: [4][5]

Browser automation from v1 is not yet part of v2

README_V2 explicitly says web-browser automation existed in v1 and will be added to v2 later. Do not assume current v2 releases provide the same UI-automation scope.

Sources: [3]

Official sources

  1. [1]karatelabs/karate repository(2026-09-30)
  2. [2]Karate README(2026-09-30)
  3. [3]Karate v2 README(2026-09-30)
  4. [4]Karate v2.1.3 parent POM(2026-09-30)
  5. [5]Karate v2.1.3 JUnit 6 POM(2026-09-30)
  6. [6]Karate v2.1.3 release(2026-09-30)
  7. [7]Karate MIT license(2026-09-30)
Supplemental curator note

Karate 2.1.3 is a stable v2 release combining API testing, mock servers, and performance testing. v2 targets Java 21+ and JUnit 6 integration. The v2 README says browser automation from v1 will be added later, so current evaluation should focus on API-oriented automation.

Try it in 3 steps

  1. 1

    Add Karate JUnit 6 2.1.3

    Add the v2 JUnit 6 integration as a test dependency in a Java 21+ Maven project.

    <dependency><groupId>io.karatelabs</groupId><artifactId>karate-junit6</artifactId><version>2.1.3</version><scope>test</scope></dependency>
  2. 2

    Write an API scenario in a feature file

    Start with one HTTP request and a status assertion.

    Feature: API Scenario: health Given url "https://example.com" When method get Then status 200
  3. 3

    Run the feature from JUnit 6

    Place the runner next to the feature package and execute it with mvn test.

    @Karate.Test Iterable<DynamicNode> testApi() { return Karate.run("api").relativeTo(getClass()); }
Check the official README

Growth

Growth trends · Last 30 days

8,972 Stars

Trend data is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • api-testing
  • assertions
  • automated-testing
  • automation
  • bdd
  • contract-testing
  • cucumber
  • developer-tools
  • load-testing
  • microservices
  • mock-server
  • test-automation
Stars
8,972
Forks
2,045
Watchers
218
Open issues
0
Owner type
Organization
Primary language
Java
License
MIT
Repository last updated
Sep 27, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?