This is useful when you ship a JAR file containing re-usable features and JavaScript / Java code and want to default a few variables that teams can inherit from. A very rare need is to be able to convert a string which happens to be in YAML form into JSON, and this can be done via the yaml type cast keyword. Normally an undefined variable results in nasty JavaScript errors. Note how karate.set() and karate.remove() below are used directly as a script statement. Here is an example: Any Karate variable will be available to the template, which is users.html in this example. There are multiple Karate API testing examples we are going to show you in this series. You can use karate.callSingle() directly in a *.feature file, but it logically fits better in the global bootstrap. to customize rebase filename and/or output), Function to be called when displaying image comparison configuration in Karate HTML reports (e.g. However, unlike Cucumber, tests aren't written in Java and are fully described in the Gherkin file. Note that the set (multiple) keyword can build complex, nested JSON (or XML) from scratch in a data-driven manner, and you may not even need to read from files for many situations. Keywords such as set and remove allow you to to tweak payload-data to fit the scenario under test. To use Playwright, you need to start a Playwright server. Also look at the section on commonly needed utilities for more ideas. You can use this to assert that it was returned within the expected time like so: Karate will attempt to parse the raw HTTP response body as JSON or XML and make it available as the response value. But since the optional() API is designed to handle the case when a given locator does not exist, you can write some very concise tests, without needing to examine the returned object from waitForAny(). """, # normal 'equality' match. ] But this totally makes sense for things not part of the main test flow and which typically need to be re-usable anyway. There are 2 variants, one that takes an integer as the param, in which case the frame is selected based on the order of appearance in the page: Or you use a locator that points to the