brine-dsl 0.8.1 → 0.9.0

data/features/assertions/is_including.feature

@@ -1,34 +0,0 @@
-Feature: Including
-  It can be asserted that a value is a superset of another value.
-
-  Scenario: Includes
-    Given a file named "features/includes.feature" with:
-      """
-
-Feature: Includes
-  Scenario: Basic object membership
-    When the response body is assigned:
-      \"\"\"
-      {"foo":"bar",
-      "baz": 1,
-      "other": "blah"}
-      \"\"\"
-    Then the value of the response body is including:
-      \"\"\"
-      {"baz":1}
-      \"\"\"
-    And the value of the response body is not including:
-      \"\"\"
-      {"missing":"value"}
-      \"\"\"
-    And the value of the response body is including `other`
-    And the value of the response body is not including `brother`
-    And the value of the response body is not including `value`
-
-      """
-    When I run `cucumber features/includes.feature`
-    Then the output should contain:
-      """
-      1 passed
-      """
-    And it should pass

data/features/assertions/is_matching.feature

@@ -1,35 +0,0 @@
-Feature: Matching
-  It can be asserted that a value matches another string or regex.
-
-  Scenario: Assorted positive and negative assertions.
-    Given a file named "features/is_matching.feature" with:
-      """
-
-Feature: Assert value matchiness.
-  Scenario: String in response body is matched against a regex.
-    When the response body is assigned:
-      \"\"\"
-      http://www.github.com?var=val
-      \"\"\"
-    Then the value of the response body is matching `/github/`
-    And the value of the response body is matching `/git.*\?.*=/`
-    And the value of the response body is not matching `/gh/`
-    And the value of the response body is not matching `/^github/`
-
-  Scenario: Regex in response body matched against a string
-    When the response body is assigned:
-      \"\"\"
-      /(.+)\1/
-      \"\"\"
-    Then the value of the response body is matching `blahblah`
-    And the value of the response body is matching `boo`
-    And the value of the response body is not matching `blah blah`
-    And the value of the response body is not matching `blah`
-
-      """
-    When I run `cucumber --strict features/is_matching.feature`
-    Then the output should contain:
-      """
-      2 passed
-      """
-    And it should pass

data/features/assertions/is_of_length.feature

@@ -1,43 +0,0 @@
-Feature: Of Length
-  It can be asserted that a value has a provided length.
-
-  Scenario: Has Length
-    Given a file named "features/has_length.feature" with:
-      """
-
-Feature: Has Length
-  Scenario: String
-    When the response body is assigned:
-      \"\"\"
-      blah
-      \"\"\"
-    Then the value of the response body is of length `4`
-
-  Scenario: Array
-    When the response body is assigned:
-      \"\"\"
-      ["foo", "blah"]
-      \"\"\"
-    Then the value of the response body is of length `2`
-
-  Scenario: Map
-    When the response body is assigned:
-      \"\"\"
-      {"foo": "blah"}
-      \"\"\"
-    Then the value of the response body is of length `1`
-
-  Scenario: Value without length attribute
-    When the response body is assigned:
-      \"\"\"
-      true
-      \"\"\"
-    Then the value of the response body is not of length `1`
-
-      """
-    When I run `cucumber features/has_length.feature`
-    Then the output should contain:
-      """
-      4 passed
-      """
-    And it should pass

data/features/assignment/parameter.feature

@@ -1,20 +0,0 @@
-Feature: A Parameter
-  An identifier can be assigned the value of the provided parameter.
-
-  Scenario: Parameter assignment.
-    Given a file named "features/parameter.feature" with:
-      """
-
-Feature: Parameter Assignment.
-  Scenario: Simple assignment.
-    Given `foo` is assigned `bar`
-    When the response body is assigned `{{ foo }}`
-    Then the value of the response body is equal to `bar`
-
-      """
-    When I run `cucumber --strict features/parameter.feature`
-    Then the output should contain:
-      """
-      1 passed
-      """
-    And it should pass

data/features/assignment/random.feature

@@ -1,25 +0,0 @@
-Feature: A Random String
-  An identifier can be assigned a random string with decent entropy.
-
-  Scenario: Random string assignment.
-    Given a file named "features/random.feature" with:
-      """
-
-Feature: Random Assignment.
-  Scenario: Several unique variables.
-    Given `v1` is assigned a random string
-    And `v2` is assigned a random string
-    And `v3` is assigned a random string
-    When the response body is assigned `[ "{{ v1 }}","{{ v2 }}","{{ v3 }}" ]`
-    Then the value of the response body does not have any element that is empty
-    And the value of the response body child `.[0]` is equal to `{{ v1 }}`
-    And the value of the response body children `.[1:2]` does not have any element that is equal to `{{ v1 }}`
-    And the value of the response body child `.[2]` is not equal to `{{ v2 }}`
-
-      """
-    When I run `cucumber --strict features/random.feature`
-    Then the output should contain:
-      """
-      8 passed
-      """
-    And it should pass

data/features/assignment/response_attribute.feature

@@ -1,33 +0,0 @@
-Feature: A Value From A Response Attribute.
-  An identifier can be assigned a value extracted from a response attribute.
-
-  Scenario: Assorted attribute extractions.
-    Given a file named "features/response_attribute.feature" with:
-      """
-
-Feature: Reponse Attribute Path Assignment.
-  Scenario: Response body.
-    Given the response body is assigned `foo`
-    When `myVar` is assigned the response body
-    And the response body is assigned `{{ myVar }}`
-    Then the value of the response body is equal to `foo`
-
-  Scenario: Response body child.
-    Given the response body is assigned `{"response": "foo"}`
-    When `myVar` is assigned the response body child `.response`
-    And the response body is assigned `{{ myVar }}`
-    Then the value of the response body is equal to `foo`
-
-  Scenario: Response body children.
-    Given the response body is assigned `{"response": "foo"}`
-    When `myVar` is assigned the response body children `.response`
-    And the response body is assigned `{{{ myVar }}}`
-    Then the value of the response body is equal to `["foo"]`
-
-      """
-    When I run `cucumber --strict features/response_attribute.feature`
-    Then the output should contain:
-      """
-      3 passed
-      """
-    And it should pass

data/features/assignment/timestamp.feature

@@ -1,33 +0,0 @@
-Feature: A Timestamp
-  An identifier can be assigned a current timestamp.
-
-  Scenario: Timestamp assignment.
-    Given a file named "features/timestamp.feature" with:
-      """
-
-Feature: Timestamp Assignment.
-  Scenario: Newer than some old date.
-    Given `v1` is assigned a timestamp
-    When the response body is assigned `{{ v1 }}`
-    Then value of the response body is greater than `2018-06-17T12:00:00Z`
-
-  Scenario: Values increase.
-    Given `v1` is assigned a timestamp
-    When the response body is assigned `{{ v1 }}`
-    Then the value of the response body is not empty
-
-    When `v2` is assigned a timestamp
-    And the response body is assigned `{{ v2 }}`
-    Then the value of the response body is greater than or equal to `{{ v1 }}`
-
-    When `v3` is assigned a timestamp
-    And the response body is assigned `{{ v3 }}`
-    Then the value of the response body is greater than or equal to `{{ v1 }}`
-    And the value of the response body is greater than or equal to `{{ v2 }}`
-
-      """
-    When I run `cucumber --strict features/timestamp.feature`
-    Then the output should contain:
-      """
-      2 passed
-      """

data/features/deprecations/replaced_with.feature

@@ -1,53 +0,0 @@
-Feature: Deprecation Messaging
-
-  Scenario: Deprecation Message is Displayed
-    Given a file named "features/deprecation.feature" with:
-    """
-Feature: Deprecation Messaging
-  Scenario: Multine String
-    When the response body is:
-      \"\"\"
-      Anything
-      \"\"\"
-    Then the response body as JSON is:
-      \"\"\"
-      ""Anything""
-      \"\"\"
-  Scenario: Multine Object
-    When the response body is:
-      \"\"\"
-      {"isObj": true}
-      \"\"\"
-    Then the response body as JSON is:
-      \"\"\"
-      '{"isObj":true}'
-      \"\"\"
-      """
-    When I run `cucumber features/deprecation.feature`
-    Then the output should contain:
-      """
-      2 passed
-      """
-    And the output should contain:
-      """
-      DEPRECATION:
-      """
-    And it should pass
-
-  Scenario: 0.9 depprecations
-    Given a file named "features/0.9.feature" with:
-      """
-
-Feature: 0.9
-  Scenario: includes the entries
-    When the response body is assigned `{"foo":"bar"}`
-    Then the response body includes the entries:
-      | foo | bar |
-
-      """
-    When I run `cucumber --strict features/0.9.feature`
-    Then the output should contain:
-      """
-      1 passed
-      """
-    And it should pass

data/features/request_construction/basic.feature

@@ -1,29 +0,0 @@
-Feature: Basic Request Construction
-  A simple request with a specified method and path can be sent.
-
-  Scenario Outline: Varying Methods
-    Given a file named "features/basic_requests.feature" with:
-
-      """
-Feature: Sending a method
-  Scenario: Basic URL
-    Given expected <method> sent to `/profile`
-
-    When a <method> is sent to `/profile`
-    Then expected calls are verified
-      """
-
-    When I run `cucumber features/basic_requests.feature`
-    Then the output should contain:
-      """
-      1 passed
-      """
-    And it should pass
-
-    Examples:
-      | method |
-      | GET    |
-      | POST   |
-      | PATCH  |
-      | DELETE |
-      | PUT    |

data/features/request_construction/body.feature

@@ -1,26 +0,0 @@
-Feature: Assigning a Request Body
-
-  Scenario: Request With Body
-    Given a file named "features/request_body.feature" with:
-      """
-Feature: Passing a body
-  Scenario: Basic URL
-    Given expected request body:
-    \"\"\"
-    {"request":1}
-    \"\"\"
-    And expected PUT sent to `/store`
-
-    When the request body is assigned:
-    \"\"\"
-    {"request":1}
-    \"\"\"
-    When a PUT is sent to `/store`
-    Then expected calls are verified
-      """
-    When I run `cucumber features/request_body.feature`
-    Then the output should contain:
-      """
-      5 passed
-      """
-    And it should pass

data/features/request_construction/clearing.feature

@@ -1,46 +0,0 @@
-Feature: Cleared After Sent
-  After a request is sent, any values that were added to that request
-are cleared and will not be present in subsequent requests.
-
-  Scenario: Request is Cleared Before Second Send
-    Given a file named "features/request_clearing.feature" with:
-
-      """
-Feature: Clearing the request.
-  Scenario: Request body is cleared.
-    Given expected request body:
-      \"\"\"
-      {"request":1}
-      \"\"\"
-    And expected PUT sent to `/profile`
-    Given expected request body:
-      \"\"\"
-      \"\"\"
-    And expected PUT sent to `/store`
-
-    When the request body is assigned:
-    \"\"\"
-    {"request":1}
-    \"\"\"
-    And a PUT is sent to `/profile`
-    And a PUT is sent to `/store`
-
-    Then expected calls are verified
-
-  Scenario: Request parameter
-    Given expected GET sent to `/query?foo=bar`
-    And expected GET sent to `/resource`
-
-    Given the request query parameter `foo` is assigned `bar`
-    And a GET is sent to `/query`
-
-    When a GET is sent to `/resource`
-    Then expected calls are verified
-      """
-
-    When I run `cucumber features/request_clearing.feature`
-    Then the output should contain:
-      """
-      2 passed
-      """
-    And it should pass

data/features/request_construction/headers.feature

@@ -1,94 +0,0 @@
-Feature: Adding Headers
-
-  Scenario: Headers are added to requests.
-    Given a file named "features/headers.feature" with:
-
-      """
-Feature: Request headers can be specified.
-  Scenario: A new header with a single value is added to request.
-    Given expected request headers:
-      \"\"\"
-      {"foo":"bar"}
-      \"\"\"
-    And expected GET sent to `/query`
-
-    When the request header `foo` is assigned `bar`
-    And a GET is sent to `/query`
-
-    Then expected calls are verified
-
-  Scenario: Default headers are present in requests.
-    Given expected request headers:
-      \"\"\"
-      {"Content-Type": "application/json"}
-      \"\"\"
-    And expected GET sent to `/query`
-
-    When a GET is sent to `/query`
-
-    Then expected calls are verified
-
-  Scenario: Default headers can be overridden.
-    Given expected request headers:
-      \"\"\"
-      {"Content-Type": "text/plain"}
-      \"\"\"
-    And expected GET sent to `/query`    
-
-    When the request header `Content-Type` is assigned `text/plain`
-    And a GET is sent to `/query`
-
-    Then expected calls are verified
-
-  Scenario: Array header values are added to requests.
-    Given expected request headers:
-      \"\"\"
-      {"X-Array": "1, 2, 3"}
-      \"\"\"
-    And expected GET sent to `/query`
-
-    When the request header `X-Array` is assigned `[1, 2, 3]`
-    And a GET is sent to `/query`
-
-    Then expected calls are verified
-
-  Scenario: The last set value for a given header wins.
-    Given expected request headers:
-      \"\"\"
-      {"foo":"baz"}
-      \"\"\"
-    And expected GET sent to `/query`
-
-    When the request header `foo` is assigned `bar`
-    And the request header `foo` is assigned `baz`
-    And a GET is sent to `/query`
-
-    Then expected calls are verified
-
-  Scenario Outline: Header is added regardless of HTTP method.
-    Given expected request headers:
-      \"\"\"
-      {"foo":"bar"}
-      \"\"\"
-    And expected <method> sent to `/query`
-
-    When the request header `foo` is assigned `bar`
-    And a <method> is sent to `/query`
-
-    Then expected calls are verified
-
-  Examples:
-    | method  |
-    | POST    |
-    | PUT     |
-    | DELETE  |
-    | HEAD    |
-    | OPTIONS |
-      """
-
-    When I run `cucumber features/headers.feature`
-    Then the output should contain:
-      """
-      10 passed
-      """
-    And it should pass