cukes-rest takes simplicity of Cucumber and provides bindings for HTTP specification. As a sugar on top, cukes-rest adds steps for storing and using request/response content from a file system, variable support in .features, context inflation in all steps and a custom plug-in system to allow users to add additional project specific content.
Feature: Gadgets are great!
Scenario: Should create another Gadget object
Given request body from file gadgets/requests/newGadget.json
And content type is "application/json"
When the client performs POST request on /gadgets
Then status code is 201
And header Location contains "http://localhost:8080/gadgets/"
When the client performs GET request on {(header.Location)}
Then status code is 200
And response contains property "id" with value other than "2000"
And response contains property "name" with value "Nexus 9"
And response does not contain property "updatedDate"
Some pretty slides can be found here!
- JDK 1.6+
<dependency>
<groupId>lv.ctco.cukesrest</groupId>
<artifactId>cukes-rest</artifactId>
<version>${cukes-rest.version}</version>
</dependency>
cukes-rest-loadrunner: experimental plugin for HP LoadRunner script generation out of cukes-rest test case
<dependency>
<groupId>lv.ctco.cukesrest</groupId>
<artifactId>cukes-rest-loadrunner</artifactId>
<version>${cukes-rest.version}</version>
</dependency>
There are two options to start local server with Sample Application:
- Run SampleApplicaiton.java with following params
server server.yml
from$MODULE_DIR$ - Execute Package/Install Maven phase of the parent project cukes-rest-all
Precondition: in order for all tests to pass successfully, please make sure you started fresh instance of Sample Application.
- To start a specific Feature/Scenario, either change CucumberOption in RunCukesTest.java or run Feature file directly from you IDE
- To start all tests run RunCukesTest.java from sub-project cukes-rest-sample
- To start all tests right from Maven, execute test phase in project cukes-rest-sample