brine-dsl 0.8.1 → 0.9.0

data/features/argument_transforms/regex.feature

@@ -1,40 +0,0 @@
-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

@@ -1,46 +0,0 @@
-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

@@ -1,51 +0,0 @@
-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

@@ -1,184 +0,0 @@
-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_empty.feature

@@ -1,67 +0,0 @@
-Feature: Empty
-  It can be asserted that a value is empty.
-
-  Scenario: Assorted positive and negative assertions pass.
-    Given a file named "features/is_empty.feature" with:
-      """
-
-Feature: Assert emptiness for multiple types.
-  Scenario: Empty body is empty.
-    When the response body is assigned ``
-    Then the value of the response body is empty
-
-  Scenario: Whitespace-only body is empty.
-    When the response body is assigned:
-      \"\"\"
-             
-      \"\"\"
-    Then the value of the response body is empty
-
-  Scenario: Empty string is empty.
-    When the response body is assigned `""`
-    Then the value of the response body is empty
-
-  Scenario: Non-empty string is not empty.
-    When the response body is assigned `blah`
-    Then the value of the response body is not empty
-
-  Scenario: Quoted whitespace is not empty.
-    When the response body is assigned `" "`
-    Then the value of the response body is not empty
-
-  Scenario: Empty arrays are empty.
-    When the response body is assigned `[]`
-    Then the value of the response body is empty
-
-  Scenario: Non-empty arrays are not empty.
-    When the response body is assigned `[[]]`
-    Then the value of the response body is not empty
-
-  Scenario: Empty objects are empty.
-    When the response body is assigned `{}`
-    Then the value of the response body is empty
-
-  Scenario: Non-empty objects are not empty.
-    When the response body is assigned `{"foo":{}}`
-    Then the value of the response body is not empty
-
-  Scenario: Null values are empty.
-    When the response body is assigned `{"foo": null}`
-    Then the value of the response body child `foo` is empty
-
-  Scenario: False is not empty.
-    When the response body is assigned `false`
-    Then the value of the response body is not empty
-
-  Scenario: 0 is not empty.
-    When the response body is assigned `0`
-    Then the value of the response body is not empty
-
-      """
-    When I run `cucumber --strict features/is_empty.feature`
-    Then the output should contain:
-      """
-      12 passed
-      """
-    And it should pass
-

data/features/assertions/is_equal_to.feature

@@ -1,60 +0,0 @@
-Feature: Equal to
-  It can be asserted that a value is equal to another value.
-
-  Scenario: Assorted positive and negative assertions pass.
-    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