Contents

Feature: manage redirect rules
  In order to be able to mock only part of api
  As a developer
  I want to redirect to real api if there are no doubles for requested fullpath

  Scenario: no redirect rules
    Given blank slate
    When I request "/api/something"
    Then I should get 404

  Scenario: add redirect rule
    Given blank slate
    When I register redirect with pattern "^/api" and uri "http://real.api.co.uk"
    And I request "/api/something"
    Then it should redirect to "http://real.api.co.uk/api/something"

  Scenario: add second redirect that match the same request
    Given there is redirect with pattern "/api/something" and uri "http://real.api.co.uk"
    When I register redirect with pattern "/api/some.*" and uri "http://real.com"
    And I request "/api/something"
    Then it should redirect to "http://real.api.co.uk/api/something"

  Scenario: add second redirect that does not match the same request
    Given there is redirect with pattern "/api/something" and uri "http://real.api.co.uk"
    When I register redirect with pattern "/api/some" and uri "http://real.com"
    And I request "/api/someth"
    Then it should redirect to "http://real.com/api/someth"

  Scenario: clear redirects
    Given there are some redirects
    When I delete all redirects
    Then there should be no redirects

Version data entries

4 entries across 4 versions & 1 rubygems

Version	Path
rest-assured-0.3.2	features/rest_api/redirects.feature
rest-assured-0.3.1	features/rest_api/redirects.feature
rest-assured-0.3.0	features/rest_api/redirects.feature
rest-assured-0.2.0	features/rest_api/redirects.feature