| layout | doc |
|---|---|
| title | REST - Codeception - Documentation |
Module for testing REST WebService.
This module can be used either with frameworks or PHPBrowser. If a framework module is connected, the testing will occur in the application directly. Otherwise, a PHPBrowser should be specified as a dependency to send requests and receive responses from a server.
- url optional - the url of api
This module requires PHPBrowser or any of Framework modules enabled.
modules:
enabled:
- REST:
depends: PhpBrowser
url: 'http://serviceapp/api/v1/'
- headers - array of headers going to be sent.
- params - array of sent data
- response - last response (string)
- Json - actions for validating Json responses (no Xml responses)
- Xml - actions for validating XML responses (no Json responses)
Conflicts with SOAP module
Adds Bearer authentication via access token.
param$accessToken[Part]json[Part]xml
Adds Digest authentication via username/password.
param$usernameparam$password[Part]json[Part]xml
Adds HTTP authentication via username/password.
param$usernameparam$password[Part]json[Part]xml
Deletes the header with the passed name. Subsequent requests will not have the deleted header in its request.
Example: {% highlight php %}
haveHttpHeader('X-Requested-With', 'Codeception'); $I->sendGET('test-headers.php'); // ... $I->deleteHeader('X-Requested-With'); $I->sendPOST('some-other-page.php'); ?>{% endhighlight %}
param string$name the name of the header to delete.
Checks over the given HTTP header and (optionally) its value, asserting that are not there
param$nameparam$value[Part]json[Part]xml
Checks that response code is not equal to provided value.
{% highlight php %}
dontSeeResponseCodeIs(200); // preferred to use \Codeception\Util\HttpCode $I->dontSeeResponseCodeIs(\Codeception\Util\HttpCode::OK); {% endhighlight %} * `[Part]` json * `[Part]` xml * `param` $code #### dontSeeResponseContains Checks whether last response do not contain text. * `param` $text * `[Part]` json * `[Part]` xml #### dontSeeResponseContainsJson Opposite to seeResponseContainsJson * `[Part]` json * `param array` $json #### dontSeeResponseJsonMatchesJsonPath Opposite to seeResponseJsonMatchesJsonPath * `param string` $jsonPath * `[Part]` json #### dontSeeResponseJsonMatchesXpath Opposite to seeResponseJsonMatchesXpath * `param string` $xpath * `[Part]` json #### dontSeeResponseMatchesJsonType Opposite to `seeResponseMatchesJsonType`. * `[Part]` json @see seeResponseMatchesJsonType * `param` $jsonType jsonType structure * `param null` $jsonPath optionally set specific path to structure with JsonPath * `Available since` 2.1.3 #### dontSeeXmlResponseEquals Checks XML response does not equal to provided XML. Comparison is done by canonicalizing both xml`s. Parameter can be passed either as XmlBuilder, DOMDocument, DOMNode, XML string, or array (if no attributes). * `param` $xml * `[Part]` xml #### dontSeeXmlResponseIncludes Checks XML response does not include provided XML. Comparison is done by canonicalizing both xml`s. Parameter can be passed either as XmlBuilder, DOMDocument, DOMNode, XML string, or array (if no attributes). * `param` $xml * `[Part]` xml #### dontSeeXmlResponseMatchesXpath Checks wheather XML response does not match XPath {% highlight php %} dontSeeXmlResponseMatchesXpath('//root/user[@id=1]'); {% endhighlight %} * `[Part]` xml * `param` $xpath #### grabAttributeFromXmlElement Finds and returns attribute of element. Element is matched by either CSS or XPath * `param` $cssOrXPath * `param` $attribute * `return` string * `[Part]` xml #### grabDataFromJsonResponse Deprecated since 2.0.9 and removed since 2.1.0 * `param` $path @throws ModuleException @deprecated #### grabDataFromResponseByJsonPath Returns data from the current JSON response using [JSONPath](http://goessner.net/articles/JsonPath/) as selector. JsonPath is XPath equivalent for querying Json structures. Try your JsonPath expressions [online](http://jsonpath.curiousconcept.com/). Even for a single value an array is returned. This method **require [`flow/jsonpath` > 0.2](https://github.com/FlowCommunications/JSONPath/) library to be installed**. Example: {% highlight php %} grabDataFromResponseByJsonPath('$..users[0].id'); $I->sendPUT('/user', array('id' => $firstUserId[0], 'name' => 'davert')); ?>{% endhighlight %}
param string$jsonPathreturnarray Array of matching itemsAvailable since2.0.9 @throws \Exception[Part]json
Returns the value of the specified header name
-
param$name -
param Boolean$first Whether to return the first value or all header values -
return string|array The first header value if$first is true, an array of values otherwise -
[Part]json -
[Part]xml
Returns current response so that it can be used in next scenario steps.
Example:
{% highlight php %}
grabResponse(); $I->sendPUT('/user', array('id' => $user_id, 'name' => 'davert')); ?>{% endhighlight %}
Available since1.1returnstring[Part]json[Part]xml
Finds and returns text contents of element. Element is matched by either CSS or XPath
param$cssOrXPathreturnstring[Part]xml
Sets HTTP header valid for all next requests. Use deleteHeader to unset it
{% highlight php %}
haveHttpHeader('Content-Type', 'application/json'); // all next requests will contain this header ?>{% endhighlight %}
param$nameparam$value[Part]json[Part]xml
Checks over the given HTTP header and (optionally) its value, asserting that are there
param$nameparam$value[Part]json[Part]xml
Checks that http response header is received only once. HTTP RFC2616 allows multiple response headers with the same name. You can check that you didn't accidentally sent the same header twice.
{% highlight php %}
seeHttpHeaderOnce('Cache-Control'); ?>>{% endhighlight %}
param$name[Part]json[Part]xml
Checks response code equals to provided value.
{% highlight php %}
seeResponseCodeIs(200); // preferred to use \Codeception\Util\HttpCode $I->seeResponseCodeIs(\Codeception\Util\HttpCode::OK); {% endhighlight %} * `[Part]` json * `[Part]` xml * `param` $code #### seeResponseContains Checks whether the last response contains text. * `param` $text * `[Part]` json * `[Part]` xml #### seeResponseContainsJson Checks whether the last JSON response contains provided array. The response is converted to array with json_decode($response, true) Thus, JSON is represented by associative array. This method matches that response array contains provided array. Examples: {% highlight php %} seeResponseContainsJson(array('name' => 'john')); // response {user: john, profile: { email: john@gmail.com }} $I->seeResponseContainsJson(array('email' => 'john@gmail.com')); ?>{% endhighlight %}
This method recursively checks if one array can be found inside of another.
param array$json[Part]json
Checks if response is exactly the same as provided.
[Part]json[Part]xmlparam$response
Checks whether last response was valid JSON. This is done with json_last_error function.
[Part]json
Checks whether last response was valid XML. This is done with libxml_get_last_error function.
[Part]xml
Checks if json structure in response matches JsonPath. JsonPath is XPath equivalent for querying Json structures. Try your JsonPath expressions online. This assertion allows you to check the structure of response json.
This method require flow/jsonpath > 0.2 library to be installed.
{% highlight json %}
{ "store": { "book": [ { "category": "reference", "author": "Nigel Rees", "title": "Sayings of the Century", "price": 8.95 }, { "category": "fiction", "author": "Evelyn Waugh", "title": "Sword of Honour", "price": 12.99 } ], "bicycle": { "color": "red", "price": 19.95 } } }
{% endhighlight %}
{% highlight php %}
seeResponseJsonMatchesJsonPath('$.store.book[*].author'); // first book in store has author $I->seeResponseJsonMatchesJsonPath('$.store.book[0].author'); // at least one item in store has price $I->seeResponseJsonMatchesJsonPath('$.store..price'); ?>{% endhighlight %}
param string$jsonPath[Part]jsonAvailable since2.0.9
Checks if json structure in response matches the xpath provided. JSON is not supposed to be checked against XPath, yet it can be converted to xml and used with XPath. This assertion allows you to check the structure of response json. * {% highlight json %}
{ "store": { "book": [ { "category": "reference", "author": "Nigel Rees", "title": "Sayings of the Century", "price": 8.95 }, { "category": "fiction", "author": "Evelyn Waugh", "title": "Sword of Honour", "price": 12.99 } ], "bicycle": { "color": "red", "price": 19.95 } } }
{% endhighlight %}
{% highlight php %}
seeResponseJsonMatchesXpath('//store/book/author'); // first book in store has author $I->seeResponseJsonMatchesXpath('//store/book[1]/author'); // at least one item in store has price $I->seeResponseJsonMatchesXpath('/store//price'); ?>{% endhighlight %}
param string$xpath[Part]jsonAvailable since2.0.9
Checks that Json matches provided types. In case you don't know the actual values of JSON data returned you can match them by type. Starts check with a root element. If JSON data is array it will check the first element of an array. You can specify the path in the json which should be checked with JsonPath
Basic example:
{% highlight php %}
seeResponseMatchesJsonType([ 'user_id' => 'integer', 'name' => 'string|null', 'is_active' => 'boolean' ]); // narrow down matching with JsonPath: // {"users": [{ "name": "davert"}, {"id": 1}]} $I->seeResponseMatchesJsonType(['name' => 'string'], '$.users[0]'); ?>{% endhighlight %}
In this case you can match that record contains fields with data types you expected. The list of possible data types:
- string
- integer
- float
- array (json object is array as well)
- boolean
You can also use nested data type structures:
{% highlight php %}
seeResponseMatchesJsonType([ 'user_id' => 'integer|string', // multiple types 'company' => ['name' => 'string'] ]); ?>{% endhighlight %}
You can also apply filters to check values. Filter can be applied with : char after the type declatation.
Here is the list of possible filters:
integer:>{val}- checks that integer is greater than {val} (works with float and string types too).integer:<{val}- checks that integer is lower than {val} (works with float and string types too).string:url- checks that value is valid url.string:date- checks that value is date in JavaScript format: https://weblog.west-wind.com/posts/2014/Jan/06/JavaScript-JSON-Date-Parsing-and-real-Datesstring:email- checks that value is a valid email according to http://emailregex.com/string:regex({val})- checks that string matches a regex provided with {val}
This is how filters can be used:
{% highlight php %}
'davert@codeception.com'} $I->seeResponseMatchesJsonType([ 'user_id' => 'string:>0:<1000', // multiple filters can be used 'email' => 'string:regex(~\@~)' // we just check that @ char is included ]); // {'user_id': '1'} $I->seeResponseMatchesJsonType([ 'user_id' => 'string:>0', // works with strings as well } ?>{% endhighlight %}
You can also add custom filters y accessing JsonType::addCustomFilter method.
See JsonType reference.
[Part]jsonAvailable since2.1.3param array$jsonTypeparam string$jsonPath
Checks XML response equals provided XML. Comparison is done by canonicalizing both xml`s.
Parameters can be passed either as DOMDocument, DOMNode, XML string, or array (if no attributes).
param$xml[Part]xml
Checks XML response includes provided XML. Comparison is done by canonicalizing both xml`s. Parameter can be passed either as XmlBuilder, DOMDocument, DOMNode, XML string, or array (if no attributes).
Example:
{% highlight php %}
seeXmlResponseIncludes("1"); ?>{% endhighlight %}
param$xml[Part]xml
Checks wheather XML response matches XPath
{% highlight php %}
seeXmlResponseMatchesXpath('//root/user[@id=1]'); {% endhighlight %} * `[Part]` xml * `param` $xpath #### sendDELETE Sends DELETE request to given uri. * `param` $url * `param array` $params * `param array` $files * `[Part]` json * `[Part]` xml #### sendGET Sends a GET request to given uri. * `param` $url * `param array` $params * `[Part]` json * `[Part]` xml #### sendHEAD Sends a HEAD request to given uri. * `param` $url * `param array` $params * `[Part]` json * `[Part]` xml #### sendLINK Sends LINK request to given uri. * `param` $url * `param array` $linkEntries (entry is array with keys "uri" and "link-param") @link http://tools.ietf.org/html/rfc2068#section-19.6.2.4 @author samva.ua@gmail.com * `[Part]` json * `[Part]` xml #### sendOPTIONS Sends an OPTIONS request to given uri. * `param` $url * `param array` $params * `[Part]` json * `[Part]` xml #### sendPATCH Sends PATCH request to given uri. * `param` $url * `param array` $params * `param array` $files * `[Part]` json * `[Part]` xml #### sendPOST Sends a POST request to given uri. Parameters and files (as array of filenames) can be provided. * `param` $url * `param array|\JsonSerializable` $params * `param array` $files * `[Part]` json * `[Part]` xml #### sendPUT Sends PUT request to given uri. * `param` $url * `param array` $params * `param array` $files * `[Part]` json * `[Part]` xml #### sendUNLINK Sends UNLINK request to given uri. * `param` $url * `param array` $linkEntries (entry is array with keys "uri" and "link-param") @link http://tools.ietf.org/html/rfc2068#section-19.6.2.4 @author samva.ua@gmail.com * `[Part]` json * `[Part]` xml #### startFollowingRedirects Enables automatic redirects to be followed by the client {% highlight php %} startFollowingRedirects(); {% endhighlight %} * `[Part]` xml * `[Part]` json #### stopFollowingRedirects Prevents automatic redirects to be followed by the client {% highlight php %} stopFollowingRedirects(); {% endhighlight %} * `[Part]` xml * `[Part]` json