brine-dsl 0.8.1 → 0.9.0

data/features/request_construction/params.feature

@@ -1,60 +0,0 @@
-@wip
-Feature: Adding Query Parameters
-
-  Scenario: Query parameters are added to requests.
-    Given a file named "features/params.feature" with:
-
-      """
-Feature: Request query parameters can be specified.
-  Scenario: A single parameter is appended to the URL.
-    Given expected GET sent to `/query?foo=bar`
-
-    When the request query parameter `foo` is assigned `bar`
-    And a GET is sent to `/query`
-
-    Then expected calls are verified
-
-  Scenario: Multiple parameters are appended to the URL with proper formatting.
-    Given expected GET sent to `/query?foo=bar&baz=1`
-
-    When the request query parameter `foo` is assigned `bar`
-    And the request query parameter `baz` is assigned `1`
-    And a GET is sent to `/query`
-
-    Then expected calls are verified
-
-  Scenario Outline: Values are encoded appropriately.
-    Given expected GET sent to `/query?foo=<encoded>`
-
-    When the request query parameter `foo` is assigned `<input>`
-    And a GET is sent to `/query`
-
-    Then expected calls are verified
-  Examples:
-    | input         | encoded                  |
-    | bar & grill   | bar+%26+grill            |
-    | + +           | %2B+%2B                  |
-    | (imbalance))  | %28imbalance%29%29       |
-
-  Scenario Outline: Parametes are added regardless of HTTP method.
-    Given expected <method> sent to `/query?foo=bar`
-
-    When the request query parameter `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/params.feature`
-    Then the output should contain:
-      """
-      10 passed
-      """
-    And it should pass

data/features/resource_cleanup/cleanup.feature

@@ -1,86 +0,0 @@
-Feature: Resource Cleanup
-  Resources created during testing can be marked for deletion.
-
-  Scenario: Initial Success
-    Given a file named "features/cleanup.feature" with:
-
-      """
-Feature: Resource Cleanup
-
-  Scenario: Successful Basic Deletion
-    Given expected DELETE sent to `/some/path`
-
-    When a resource is created at `/some/path`
-      """
-
-    When I run `cucumber --strict features/cleanup.feature`
-    Then the output should match %r<delete http://www.example.com/some/path>
-    And the output should not contain:
-      """
-      ERROR
-      """
-    And it should pass
-
-  Scenario: Returned 4xx
-    Given a file named "features/cleanup_failure.feature" with:
-
-      """
-Feature: Resource Cleanup
-
-  Scenario: Failed Deletion
-    Given expected response status of `409`
-    And expected DELETE sent to `/some/path`
-
-    When a resource is created at `/some/path`
-      """
-
-    When I run `cucumber --strict features/cleanup_failure.feature`
-    Then the output should match %r<(?:.*delete http://www.example.com/some/path.*){3}>
-    And the output should contain:
-      """
-      ERROR
-      """
-    And it should pass
-
-  Scenario: Success Upon Retry
-    Given a file named "features/cleanup_retried.feature" with:
-
-      """
-Feature: Resource Cleanup
-
-  Scenario: Success Upon Retry
-    Given expected response status sequence of `[504, 200]`
-    And expected DELETE sent to `/some/path`
-
-    When a resource is created at `/some/path`
-      """
-
-    When I run `cucumber --strict -o ../../out.log features/cleanup_retried.feature`
-    Then the output should match %r<(?:.*delete http://www.example.com/some/path.*){2}>
-    And the output should not contain:
-      """
-      ERROR
-      """
-    And it should pass
-
-
-  Scenario: Unreached Success
-    Given a file named "features/cleanup_unreached.feature" with:
-
-      """
-Feature: Resource Cleanup
-
-  Scenario: Unreached Success
-    Given expected response status sequence of `[504, 504, 504, 200]`
-    And expected DELETE sent to `/some/path`
-
-    When a resource is created at `/some/path`
-      """
-
-    When I run `cucumber --strict -o ../../out.log features/cleanup_unreached.feature`
-    Then the output should match %r<(?:.*delete http://www.example.com/some/path.*){3}>
-    And the output should contain:
-      """
-      ERROR
-      """
-    And it should pass    

data/features/selectors/all.feature

@@ -1,55 +0,0 @@
-Feature: All Elements
-  Assertions can be done against all elements of a structure.
-
-  Scenario: Assorted positive and negative assertions.
-    Given a file named "features/all.feature" with:
-      """
-
-Feature: Allow selection of all structure elements
-  Scenario: List in response body
-    When the response body is assigned:
-      \"\"\"
-      ["a", "bb", "ccc"]
-      \"\"\"
-    Then the value of the response body has elements which are all matching `/\w+/`
-
-  Scenario: Spread nested lists
-    When the response body is assigned:
-      \"\"\"
-      [{"val": "foo"},{"val": "foo"}]
-      \"\"\"
-    Then the value of the response body children `..val` has elements which are all equal to `foo`
-
-      """
-    When I run `cucumber --strict features/all.feature`
-    Then the output should contain:
-      """
-      4 passed
-      """
-    And it should pass
-
-  Scenario: Failing tests since negation isn't available yet.
-    Given a file named "features/all.feature" with:
-      """
-
-Feature: Allow selection of all structure elements
-  Scenario: List in response body
-    When the response body is assigned:
-      \"\"\"
-      ["a", "bb", "ccc"]
-      \"\"\"
-    Then the value of the response body has elements which are all matching `/^\w$/`
-
-  Scenario: Spread nested lists
-    When the response body is assigned:
-      \"\"\"
-      [{"val": "foo"},{"val": "fob"}]
-      \"\"\"
-    Then the value of the response body children `..val` has elements which are all equal to `foo`
-
-      """
-    When I run `cucumber --strict features/all.feature`
-    Then the output should contain:
-      """
-      2 failed
-      """

data/features/selectors/any.feature

@@ -1,48 +0,0 @@
-Feature: Any Element
-  Assertions can be done against any element of a structure.
-
-  Scenario: Assorted positive and negative assertions.
-    Given a file named "features/any.feature" with:
-      """
-
-Feature: Allow selection of any structure element
-  Scenario: List in response body
-    When the response body is assigned:
-      \"\"\"
-      ["a", "b", "c"]
-      \"\"\"
-    Then the value of the response body does have any element that is equal to `a`
-    And the value of the response body does not have any element that is equal to `d`
-
-  Scenario: Nested list in response body
-    When the response body is assigned:
-      \"\"\"
-      {"letters": ["a", "b", "c"]}
-      \"\"\"
-    Then the value of the response body child `letters` does have any element that is equal to `a`
-    And the value of the response body child `letters` does not have any element that is equal to `d`
-
-  Scenario: Map matches entries
-    When the response body is assigned:
-      \"\"\"
-      {"a": 1, "b": 2}
-      \"\"\"
-    #Equality will match keys
-    Then the value of the response body does have any element that is equal to `a`
-    And the value of the response body does not have any element that is equal to `d`
-
-  Scenario: Spread nested lists
-    When the response body is assigned:
-      \"\"\"
-      [{"val":"foo"},{"val":"bar"}]
-      \"\"\"
-    Then the value of the response body children `..val` does have any element that is equal to `foo`
-    And the value of the response body children `..val` does not have any element that is equal to `other`
-
-      """
-    When I run `cucumber --strict features/any.feature`
-    Then the output should contain:
-      """
-      4 passed
-      """
-    And it should pass

data/features/step_definitions/test_steps.rb

@@ -1,5 +0,0 @@
-# the output should contain: is useful for seeing failures
-# TODO: Swap this out with standard aruba step
-Then(/^it should pass$/) do
-  expect(last_command_started).to be_successfully_executed
-end

data/features/support/env.rb

@@ -1,10 +0,0 @@
-require 'aruba/cucumber'
-
-Before do
-  write_file 'features/support/env.rb',
-             <<-END
-             require 'brine'
-             require 'brine/test_steps'
-             World(brine_mix)
-             END
-end

data/tutorial/missing.feature

@@ -1,5 +0,0 @@
-Feature: Absent resources return 404s.
-
-  Scenario: A request for a known missing resource.
-    When a GET is sent to `/bins/brine-absent`
-    Then the value of the response status is equal to `404`

data/tutorial/post_matching.feature

@@ -1,12 +0,0 @@
-Feature: A POST returns a link to the created resource.
-
-  Scenario: A valid post.
-    When the request body is assigned:
-      """
-      {"name": "boolean-setting",
-       "value": true}
-      """
-    And a POST is sent to `/bins`
-
-    Then the value of the response status is equal to `201`
-    And the value of the response body child `uri` is matching `/https://api.myjson.com/bins/\w+/`

data/tutorial/post_status.feature

@@ -1,10 +0,0 @@
-Feature: A POST returns a 201.
-
-  Scenario: A valid post.
-    When the request body is assigned:
-      """
-      {"name": "boolean-setting",
-       "value": true}
-      """
-    And a POST is sent to `/bins`
-    Then the value of the response status is equal to `201`

data/tutorial/support/env.rb

@@ -1,2 +0,0 @@
-require 'brine'
-World(brine_mix)