Sha256: 743e42431f2bca3990b2eae2948532584cdf6ab6351317bde413603996ee4e54

Contents?: true

Size: 1004 Bytes

Versions: 10

Compression:

Stored size: 1004 Bytes

Contents

Feature: Persistence
  In order to persist fixtrures/redirects between service restarts
  As a developer
  I want to be able to specify persistent storage

  Scenario: default storage
    Given I start service without --database option
    And I register "/api/something" as fullpath and "content" as response content
    And I restart service without --database option
    When I request "/api/something"
    Then I should get 404 in response status

  Scenario Outline: specify storage
    Given I start service with --database "<db>" option
    And I register "/api/something" as fullpath and "content" as response content
    And I restart service with --database "<db2>" option
    When I request "/api/something"
    Then I should get <status> in response status

    Examples:
      | db               | db2              | status |
      | database.db      | database.db      | 200    |
      | /tmp/database.db | /tmp/database.db | 200    |
      | database.db      | database2.db     | 404    |

Version data entries

10 entries across 10 versions & 1 rubygems

Version Path
rest-assured-0.2.0.rc5 features/persistence.feature
rest-assured-0.2.0.rc4 features/persistence.feature
rest-assured-0.2.0.rc3 features/persistence.feature
rest-assured-0.2.0.rc2 features/persistence.feature
rest-assured-0.2.0.rc1 features/persistence.feature
rest-assured-0.1.4 features/persistence.feature
rest-assured-0.1.3 features/persistence.feature
rest-assured-0.1.2 features/persistence.feature
rest-assured-0.1.1 features/persistence.feature
rest-assured-0.1.0 features/persistence.feature