brine-dsl 0.5.0

data/features/argument_transforms/boolean.feature

@@ -0,0 +1,37 @@
+Feature: An argument that could represent a boolean value will be
+    transformed into a boolean type.
+
+  Scenario Outline: Assorted basic inputs are provided.
+    Given a file named "features/transform_boolean.feature" with:
+      """
+
+Feature: Transform boolean arguments.
+  Scenario: Docstring simple value.
+    When the response body is assigned:
+      \"\"\"
+      <input>
+      \"\"\"
+    Then the response body as JSON is:
+      \"\"\"
+      '<expected>'
+      \"\"\"
+
+  Scenario: Inline simple value.
+    When the response body is assigned `<input>`
+    Then the response body as JSON is:
+      \"\"\"
+      '<expected>'
+      \"\"\"
+
+      """
+    When I run `cucumber --strict features/transform_boolean.feature`
+    Then the output should contain:
+      """
+      2 passed
+      """
+    And it should pass
+
+    Examples:
+      | input     | expected |
+      | true      | true     |
+      | false     | false    |

data/features/argument_transforms/datetime.feature

@@ -0,0 +1,45 @@
+Feature: An argument that could represent a date/time value will be
+    transformed into a time type.
+
+  Scenario: Assorted basic inputs are provided.
+    Given a file named "features/transform_datetime.feature" with:
+      """
+
+Feature: Transform date/time arguments.
+  Scenario: Docstring datetime is serialized properly.
+    When the response body is assigned:
+      \"\"\"
+      2017-01-01T09:00:00Z
+      \"\"\"
+    Then the response body as JSON is:
+      \"\"\"
+      '"2017-01-01 09:00:00 UTC"'
+      \"\"\"
+
+  Scenario: Inline datetime is serialized properly.
+    When the response body is assigned `2017-01-01T09:00:00Z`
+    Then the response body as JSON is:
+      \"\"\"
+      '"2017-01-01 09:00:00 UTC"'
+      \"\"\"
+
+  Scenario: Value Comparison
+    When `now` is assigned a timestamp
+    And `then` is assigned `2017-01-01T12:00:00Z`
+    Then the value of `{{then}}` is less than `{{now}}`
+
+  Scenario: Child Comparison
+    When `now` is assigned a timestamp
+    And the response body is assigned:
+      \"\"\"
+      {"my_timestamp": "{{now}}"}
+      \"\"\"
+    Then the value of the response body child `my_timestamp` is greater than `2017-01-01T12:00:00Z`
+
+      """
+    When I run `cucumber --strict features/transform_datetime.feature`
+    Then the output should contain:
+      """
+      4 passed
+      """
+    And it should pass

data/features/argument_transforms/integer.feature

@@ -0,0 +1,41 @@
+Feature: An argument that could represent an integer will be
+    transformed into an integer type.
+
+  Scenario Outline: Assorted basic inputs are provided.
+    Given a file named "features/transform_integer.feature" with:
+      """
+
+Feature: Transform integer arguments.
+  Scenario: Docstring simple value.
+    When the response body is assigned:
+      \"\"\"
+      <input>
+      \"\"\"
+    Then the response body as JSON is:
+      \"\"\"
+      '<expected>'
+      \"\"\"
+
+  Scenario: Inline simple value.
+    When the response body is assigned `<input>`
+    Then the response body as JSON is:
+      \"\"\"
+      '<expected>'
+      \"\"\"
+
+      """
+    When I run `cucumber --strict features/transform_integer.feature`
+    Then the output should contain:
+      """ar
+      2 passed
+      """
+    And it should pass
+
+    Examples:
+      |               input |            expected |
+      |                   0 |                   0 |
+      |                  -0 |                   0 |
+      |                  10 |                  10 |
+      |                 -10 |                 -10 |
+      |  123456789123456789 |  123456789123456789 |
+      | -123456789123456789 | -123456789123456789 |

data/features/argument_transforms/list.feature

@@ -0,0 +1,46 @@
+Feature: An argument that could represent a JSON list will be
+    transformed into a list whose elements will be also be transformed.
+
+  Scenario Outline: Assorted basic inputs are provided.
+    Given a file named "features/transform_list.feature" with:
+      """
+
+Feature: Transform list arguments.
+  Scenario: Docstring simple list.
+    When the response body is assigned:
+      \"\"\"
+      <input>
+      \"\"\"
+    Then the response body as JSON is:
+      \"\"\"
+      '<expected>'
+      \"\"\"
+
+  Scenario: Inline simple list.
+    When the response body is assigned `<input>`
+    Then the response body as JSON is:
+      \"\"\"
+      '<expected>'
+      \"\"\"
+
+      """
+    When I run `cucumber --strict features/transform_list.feature`
+    Then the output should contain:
+      """
+      2 passed
+      """
+    And it should pass
+
+    Examples:
+      | input                   | expected                |
+      | []                      | []                      |
+      | ["a", "b"]              | ["a","b"]               |
+      | ["a"  ,  "b" ]          | ["a","b"]               |
+      | ["  a", " b "]          | ["  a"," b "]           |
+      | [true, "false"]         | [true,"false"]          |
+      | [1,-3,"-5"]             | [1,-3,"-5"]             |
+      | ["foo,bar","baz"]       | ["foo,bar","baz"]       |
+      | ["foo,bar,baz"]         | ["foo,bar,baz"]         |
+      | ["foo\\"","bar"]        | ["foo\\"","bar"]        |
+      | ["fo\\"o\\",bar","baz"] | ["fo\\"o\\",bar","baz"] |
+      | [{"i":1},{"i":2}, "h"]  | [{"i":1},{"i":2},"h"]   |

data/features/argument_transforms/object.feature

@@ -0,0 +1,66 @@
+Feature: An argument that could represent a JSON object will be
+    transformed into an object whose elements will also be transformed.
+
+  Scenario Outline: Assorted basic inputs are provided.
+    Given a file named "features/transform_object.feature" with:
+      """
+
+Feature: Transform object arguments.
+  Scenario: Docstring simple object.
+    When the response body is assigned:
+      \"\"\"
+      <input>
+      \"\"\"
+    Then the response body as JSON is:
+      \"\"\"
+      '<expected>'
+      \"\"\"
+
+  Scenario: Inline simple object.
+    When the response body is assigned `<input>`
+    Then the response body as JSON is:
+      \"\"\"
+      '<expected>'
+      \"\"\"
+
+      """
+    When I run `cucumber features/transform_object.feature`
+    Then the output should contain:
+      """
+      2 passed
+      """
+    And it should pass
+
+    Examples:
+      | input                                               | expected                                      |
+      | {}                                                  | {}                                            |
+      | {"a":1}                                             | {"a":1}                                       |
+      | {"foo":"bar", "num":1, "list": ["1", 2, true]}      | {"foo":"bar","num":1,"list":["1",2,true]}     |
+      | {"foo": {"bar":{ "num":1, "list": ["1", 2, true]}}} | {"foo":{"bar":{"num":1,"list":["1",2,true]}}} |
+      | {"foo": "\"list\": [\"1\", 2, true]"}               | {"foo":"\\"list\\": [\\"1\\", 2, true]"}      |
+            
+  Scenario: Passed an Object split over multiple lines
+    Given a file named "features/transform_object_splitline.feature" with:
+      """
+
+Feature: Using an object argument split over multiple lines
+  Scenario: Object split over lines
+    When the response body is assigned:
+      \"\"\"
+      {
+        "foo":"bar"
+      }
+      \"\"\"
+    Then the value of the response body is equal to:
+      \"\"\"
+      {"foo":"bar"}
+      \"\"\"
+
+      """
+    When I run `cucumber --strict features/transform_object_splitline.feature`
+    Then the output should contain:
+      """
+      1 passed
+      """
+    And it should pass
+            

data/features/argument_transforms/quoted.feature

@@ -0,0 +1,41 @@
+Feature: An argument that is quoted will be (not) transformed into
+    into a string, regardless of any more specific data type the
+    quoted value may resemble.
+
+  Scenario Outline: Assorted basic inputs are provided.
+    Given a file named "features/transform_quoted.feature" with:
+      """
+
+Feature: Transform quoted arguments.
+  Scenario: Docstring simple value.
+    When the response body is assigned:
+      \"\"\"
+      <input>
+      \"\"\"
+    Then the response body as JSON is:
+      \"\"\"
+      '<expected>'
+      \"\"\"
+
+    Scenario: Inline simple value.
+      When the response body is assigned `<input>`
+      Then the response body as JSON is:
+        \"\"\"
+        '<expected>'
+        \"\"\"
+
+      """
+    When I run `cucumber --strict features/transform_quoted.feature`
+    Then the output should contain:
+      """
+      2 passed
+      """
+    And it should pass
+
+    Examples:
+      | input               | expected            |
+      | "true"              | "true"              |
+      | "123"               | "123"               |
+      | " -123 "            | " -123 "            |
+      | "["foo","bar"]"     | "[\"foo\",\"bar\"]" |
+      | "{"foo":"bar"}"     | "{\"foo\":\"bar\"}" |

data/features/argument_transforms/regex.feature

@@ -0,0 +1,40 @@
+Feature: An argument that is enclosed in slashes (/) will be transformed into a regex.
+
+  Scenario Outline: Assorted basic inputs are provided.
+    Given a file named "features/transform_regex.feature" with:
+      """
+
+Feature: Tranform regex arguments.
+  Scenario: Docstring simple value.
+    When the response body is assigned:
+      \"\"\"
+      <input>
+      \"\"\"
+    Then the response body as JSON is:
+      \"\"\"
+      '<expected>'
+      \"\"\"
+
+  Scenario: Inline simple value.
+    When the response body is assigned `<input>`
+    Then the response body as JSON is:
+      \"\"\"
+      '<expected>'
+      \"\"\"
+
+      """
+    When I run `cucumber --strict features/transform_regex.feature`
+    Then the output should contain:
+      """
+      2 passed
+      """
+    And it should pass
+
+    #Expecting Ruby stringification and using painful escaping
+    Examples:
+      | input             | expected                                            |
+      | //                | "(?-mix:)"                                          |
+      | /\//              | "(?-mix:\\\\\\\\/)"                                 |
+      | /.*/              | "(?-mix:.*)"                                        |
+      | /"[[:alpha:]]?"/  | "(?-mix:\\\\"[[:alpha:]]?\\\\")"                    |
+      | /foo bar/         | "(?-mix:foo bar)"                                   |

data/features/argument_transforms/template.feature

@@ -0,0 +1,46 @@
+Feature: An argument that includes {{ }} interpolation markers will be
+    treated as a template and transformed into an evaluated version of
+    that template using the current binding environment which will then
+    also be transformed.
+
+  Scenario Outline: A single value template is expanded
+      using a simple bound value.
+    Given a file named "features/transform_template.feature" with:
+      """
+
+Feature: Transform template arguments.
+  Background:
+    When `bound` is assigned `<binding>`
+
+  Scenario: Docstring single value template.
+    When the response body is assigned:
+      \"\"\"
+      {{{bound}}}
+      \"\"\"
+    Then the response body as JSON is:
+      \"\"\"
+      '<expected>'
+      \"\"\"
+  Scenario: Inline single value template.
+    When the response body is assigned `{{{bound}}}`
+    Then the response body as JSON is:
+      \"\"\"
+      '<expected>'
+      \"\"\"
+
+      """
+    When I run `cucumber --strict features/transform_template.feature`
+    Then the output should contain:
+      """
+      6 passed
+      """
+    And it should pass
+
+    # Double quotes for quoted because it will be transformed on binding also
+    Examples:
+      | binding        | expected  |
+      | true           | true      |
+      | -452           | -452      |
+      | ""-452""       | "-452"    |
+      | ["a", 1]       | ["a",1]   |
+      | ""["a", 1]""     | "[\\"a\\", 1]" |

data/features/argument_transforms/whitespace.feature

@@ -0,0 +1,51 @@
+Feature: An argument that includes leading or trailing whitespace
+    will be transformed so that such whitespace is removed
+    and that value will also be transformed.
+
+  Scenario Outline: Assorted basic inputs are provided.
+    Given a file named "features/transform_whitespace.feature" with:
+      """
+
+Feature: Transform arguments with leading and/or trailing whitespace.
+  Scenario: Docstring simple value.
+    When the response body is assigned:
+      \"\"\"
+      <input>
+      \"\"\"
+    Then the response body as JSON is:
+      \"\"\"
+      '<expected>'
+      \"\"\"
+
+  Scenario: Inline simple value.
+    When the response body is assigned `<input>`
+    Then the response body as JSON is:
+      \"\"\"
+      '<expected>'
+      \"\"\"
+
+  Scenario: Docstring value with a leading and trailing line.
+    When the response body is assigned:
+    \"\"\"
+
+    <input>
+
+    \"\"\"
+    Then the response body as JSON is:
+    \"\"\"
+    '<expected>'
+    \"\"\"
+
+      """
+    When I run `cucumber --strict features/transform_whitespace.feature`
+    Then the output should contain:
+      """
+      3 passed
+      """
+    And it should pass
+
+    Examples:
+      | input                     | expected     |
+      | 	true              | true         |
+      |   123	                  | 123          |
+      |  ["a"]	                  | ["a"]        |

data/features/assertions/is_a_valid.feature

@@ -0,0 +1,184 @@
+Feature: A valid ...
+
+  Scenario: Positive and negative assertions for JSON types.
+    Given a file named "features/is_a_valid.feature" with:
+      """
+
+Feature: Assert type validity
+  Scenario: String in response body is only a valid String.
+    When the response body is assigned:
+      \"\"\"
+      foo
+      \"\"\"
+    Then the value of the response body is a valid `String`
+    And the value of the response body is not a valid `Number`
+    And the value of the response body is not a valid `Integer`
+    And the value of the response body is not a valid `Object`
+    And the value of the response body is not a valid `Array`
+    And the value of the response body is not a valid `Boolean`
+
+  Scenario: Integer in response body is a valid Integer and Number.
+    When the response body is assigned:
+      \"\"\"
+      1
+      \"\"\"
+    Then the value of the response body is not a valid `String`
+    And the value of the response body is a valid `Number`
+    And the value of the response body is a valid `Integer`
+    And the value of the response body is not a valid `Object`
+    And the value of the response body is not a valid `Array`
+    And the value of the response body is not a valid `Boolean`
+
+  Scenario: Quoted Number in response body is only a valid String.
+    When the response body is assigned:
+      \"\"\"
+      "1"
+      \"\"\"
+    Then the value of the response body is a valid `String`
+    And the value of the response body is not a valid `Number`
+    And the value of the response body is not a valid `Integer`
+    And the value of the response body is not a valid `Object`
+    And the value of the response body is not a valid `Array`
+    And the value of the response body is not a valid `Boolean`
+
+  Scenario: Empty Object in response body is only a valid Object.
+    When the response body is assigned:
+      \"\"\"
+      {}
+      \"\"\"
+    Then the value of the response body is not a valid `String`
+    And the value of the response body is not a valid `Number`
+    And the value of the response body is not a valid `Integer`
+    And the value of the response body is a valid `Object`
+    And the value of the response body is not a valid `Array`
+    And the value of the response body is not a valid `Boolean`
+
+  Scenario: Object in response body is only a valid Object.
+    When the response body is assigned:
+      \"\"\"
+      {"foo": 1}
+      \"\"\"
+    Then the value of the response body is not a valid `String`
+    And the value of the response body is not a valid `Number`
+    And the value of the response body is not a valid `Integer`
+    And the value of the response body is a valid `Object`
+    And the value of the response body is not a valid `Array`
+    And the value of the response body is not a valid `Boolean`
+
+  Scenario: Quoted Object in response body is only a valid String.
+    When the response body is assigned:
+      \"\"\"
+      "{"foo": 1}"
+      \"\"\"
+    Then the value of the response body is a valid `String`
+    And the value of the response body is not a valid `Number`
+    And the value of the response body is not a valid `Integer`
+    And the value of the response body is not a valid `Object`
+    And the value of the response body is not a valid `Array`
+    And the value of the response body is not a valid `Boolean`
+
+
+  Scenario: Empty Array in response body is only a valid Array.
+    When the response body is assigned:
+      \"\"\"
+      []
+      \"\"\"
+    Then the value of the response body is not a valid `String`
+    And the value of the response body is not a valid `Number`
+    And the value of the response body is not a valid `Integer`
+    And the value of the response body is not a valid `Object`
+    And the value of the response body is a valid `Array`
+    And the value of the response body is not a valid `Boolean`
+
+  Scenario: Array in response body is only a valid Array.
+    When the response body is assigned:
+      \"\"\"
+      [1, "foo"]
+      \"\"\"
+    Then the value of the response body is not a valid `String`
+    And the value of the response body is not a valid `Number`
+    And the value of the response body is not a valid `Integer`
+    And the value of the response body is not a valid `Object`
+    And the value of the response body is a valid `Array`
+    And the value of the response body is not a valid `Boolean`
+
+  Scenario: true in response body is only a valid Boolean.
+    When the response body is assigned:
+      \"\"\"
+      true
+      \"\"\"
+    Then the value of the response body is not a valid `String`
+    And the value of the response body is not a valid `Number`
+    And the value of the response body is not a valid `Integer`
+    And the value of the response body is not a valid `Object`
+    And the value of the response body is not a valid `Array`
+    And the value of the response body is a valid `Boolean`
+
+  Scenario: false in response body is only a valid Boolean.
+    When the response body is assigned:
+      \"\"\"
+      false
+      \"\"\"
+    Then the value of the response body is not a valid `String`
+    And the value of the response body is not a valid `Number`
+    And the value of the response body is not a valid `Integer`
+    And the value of the response body is not a valid `Object`
+    And the value of the response body is not a valid `Array`
+    And the value of the response body is a valid `Boolean`
+
+  Scenario: null in response body is not any valid type.
+    When the response body is assigned:
+      \"\"\"
+      [null]
+      \"\"\"
+    Then the value of the response body child `[0]` is not a valid `String`
+    And the value of the response body child `[0]` is not a valid `Number`
+    And the value of the response body child `[0]` is not a valid `Integer`
+    And the value of the response body child `[0]` is not a valid `Object`
+    And the value of the response body child `[0]` is not a valid `Array`
+    And the value of the response body child `[0]` is not a valid `Boolean`
+
+  Scenario: Selected Array child is a valid Array.
+    When the response body is assigned:
+      \"\"\"
+      {"val": [1, 2, 3]}
+      \"\"\"
+    Then the value of the response body child `val` is a valid `Array`
+
+  Scenario: Selected Array child member is a valid String.
+    When the response body is assigned:
+      \"\"\"
+      {"val": [1, 2, 3]}
+      \"\"\"
+    Then the value of the response body child `val[0]` is a valid `Number`
+    Then the value of the response body child `val[0]` is a valid `Integer`
+
+  Scenario: Selected nested children are a valid Array.
+    When the response body is assigned:
+      \"\"\"
+      [{"val": 1},{"val": 2}]
+      \"\"\"
+    Then the value of the response body children `.val` is a valid `Array`
+
+  Scenario: Selected nested children can be tested for type.
+    When the response body is assigned:
+      \"\"\"
+      [{"val": 1},{"val": 2}]
+      \"\"\"
+    Then the value of the response body children `.val` has elements which are all a valid `Number`
+    Then the value of the response body children `.val` has elements which are all a valid `Integer`
+
+  Scenario: Selected nested children can be tested for type when Arrays.
+    When the response body is assigned:
+      \"\"\"
+      [{"val": [1]},{"val": [2]}]
+      \"\"\"
+    Then the value of the response body children `.val` has elements which are all a valid `Array`
+
+      """
+    When I run `cucumber --strict features/is_a_valid.feature`
+    Then the output should contain:
+      """
+      16 passed
+      """
+    And it should pass

data/features/assertions/is_equal_to.feature

@@ -0,0 +1,60 @@
+Feature: Equal to
+  It can be asserted that a value is equal to another value
+
+  Scenario: Assorted positive and negative assertions.
+    Given a file named "features/is_equal_to.feature" with:
+      """
+
+Feature: Assert value equality
+  Scenario: String in response body
+    When the response body is assigned:
+      \"\"\"
+      foo
+      \"\"\"
+    Then the value of the response body is equal to `foo`
+    And the value of the response body is not equal to `foot`
+
+  Scenario: Response Status
+    When the response status is assigned `404`
+    Then the value of the response status is equal to `404`
+    And the value of the response status is not equal to `200`
+
+  Scenario: Object in response body
+    When the response body is assigned:
+      \"\"\"
+      {
+        "foo": "bar"
+      }
+      \"\"\"
+    Then the value of the response body is equal to:
+      \"\"\"
+      {"foo":"bar"}
+      \"\"\"
+    And the value of the response body is not equal to:
+      \"\"\"
+      {"foo": "baz"}
+      \"\"\"
+
+  Scenario: List in response body
+    When the response body is assigned `[1, "foo", true]`
+    Then the value of the response body is equal to `[1, "foo", true]`
+    And the value of the response body is not equal to `[1, "bar", true]`
+
+  Scenario Outline: Objects must match completely
+    When the response body is assigned `{"foo": "bar", "baz": 1}`
+    Then the value of the response body is not equal to `<comparison>`
+
+  Examples:
+    | comparison                           |
+    | {}                                   |
+    | {"foo": "bar"}                       |
+    | {"foo": "bar", "baz": 1, "extra": 2} |
+    | {"foo": "bar", "baz": 2}             |
+
+      """
+    When I run `cucumber --strict features/is_equal_to.feature`
+    Then the output should contain:
+      """
+      8 passed
+      """
+    And it should pass