Note how we unpack the kittens and use it to data drive the Scenario Outline. It will create a Karate report under Karate Project > target > Karate report > karate-summary.html, Step 4: Create a TestRunner.java class under src/test/java. Note how we can even serve an image with the right Content-Type header. Assuming you use JUnit, there are some good reasons for the recommended (best practice) naming convention and choice of file-placement shown above: For details on what actually goes into a script or *.feature file, refer to the syntax guide. The webDriverUrl driver configuration key is optional, but if specified, will be used as the W3C WebDriver remote server. Here is an example: testCompile 'com.intuit.karate:karate-junit5:1.3.1', systemProperty "karate.options", System.properties.getProperty("karate.options"), systemProperty "karate.env", System.properties.getProperty("karate.env"), "ch.qos.logback.classic.filter.ThresholdFilter", // don't waste time waiting for a connection or if servers don't respond within 5 seconds, # steps here are executed before each Scenario in this file, # variables defined here will be 'global' to all scenarios, # and will be re-initialized before every scenario, # assigning a number (you can use '*' instead of Given / When / Then). This is typically combined with multipart file as shown below. Think of it as just like waitFor() but without the wait part. # behind the scenes, it could be creating (or over-writing) a bunch of variables ! This will give you the usual HTML report showing what features will be run, including all steps shown (including comments) so that it can be reviewed. Just triggers a click event on the DOM element: You can use this for plain-vanilla