Stop copying Karate API tests: use Scenario Outline with Examples
Run one Karate API scenario against many inputs using Scenario Outline and Examples tables instead of duplicating feature files.
Loading…
ReadMeFeed / Community knowledge
#karate-dsl
Real questions. Useful conversations. Find the people who know your stack.
karatelabsData-Driven API Testing in Karate DSL: Scenario Outline with External Data Sources
Karate DSL's Scenario Outline with Examples tables lets you drive one API test from external CSV or JSON files. This guide shows a complete worked example, covers parallel execution, data transformation, and the limits you'll hit at scale.
Mastering Karate’s Call Feature: Reusable Test Logic in a Single Feature File
Use Karate's call and callonce to reuse feature logic, pass JSON data, and capture return values. Learn how to structure calls, avoid pitfalls, and verify results with the HTML report.
Troubleshooting Connection Refused and Host Resolution Errors in Karate DSL
A diagnostic guide for resolving 'Unable to resolve host' and 'Connection Refused' errors in Karate DSL, focusing on DNS, JVM proxy settings, and environment configuration.
Data‑Driven API Testing with Karate DSL: Using Scenario Outline and Examples
Learn how Karate DSL’s Scenario Outline and Examples let you run the same API test with many data sets, producing distinct scenarios and clean reports without writing loops.
Reusing Authentication Tokens Across Karate Scenarios with callSingle
Learn how to cache a login token once per thread using Karate's callSingle, avoid repeated authentication calls, and understand its limits when state changes.
Reusing Authentication in Karate DSL with the call Keyword
Learn how to eliminate duplicated login steps in Karate DSL by extracting authentication into a reusable feature and invoking it with the call keyword.
Debugging 'Assertion Failed' and 'Unexpected Response' Errors in Karate DSL
A diagnostic guide for resolving 'Assertion Failed' and 'Unexpected Response' errors in Karate DSL, focusing on JSON path validation, type mismatches, and fuzzy matchers.
Karate `read()` CSV data loading with Scenario Outline pagination: unbounded memory risk
Karate Scenario Outlines driven by `read()` load entire CSV or JSON files into the heap before iteration begins. This design means a 100 kB test data file can trigger OutOfMemoryError under constrained -Xmx settings, and no public API exists for lazy row extraction or bounded iteration. The framework's pagination support for REST API responses requires manua