Sha256: 3ea5c2e95469e2c7ee5f8c891e27714f87569a32ee05baa3595367f6a676f2ff

Contents?: true

Size: 779 Bytes

Versions: 13

Compression:

Stored size: 779 Bytes

Contents

Feature: Push Features To Server
  In order to easily get features on the server
  As a developer
  I want to be able to push features to an endpoint

  Scenario: Push features without authentication
    Given I don't have a .wally authorisation file
    When I put data to /features with the authentication code
    Then I should get a 403 http status

  Scenario: Push features with authentication
    Given I have a .wally authentication file
    When I put data to /features with the authentication code
    Then I should get a 201 http status

  Scenario: Pushed features show up on home page
    Given I have a .wally authentication file
    When I put data to /features with the authentication code
    And I visit the home page
    Then I should see the uploaded feature

Version data entries

13 entries across 13 versions & 1 rubygems

Version Path
wally-0.0.33 features/push_features.feature
wally-0.0.32 features/push_features.feature
wally-0.0.31 features/push_features.feature
wally-0.0.30 features/push_features.feature
wally-0.0.29 features/push_features.feature
wally-0.0.28 features/push_features.feature
wally-0.0.27 features/push_features.feature
wally-0.0.26 features/push_features.feature
wally-0.0.25 features/push_features.feature
wally-0.0.24 features/push_features.feature
wally-0.0.22 features/push_features.feature
wally-0.0.21 features/push_features.feature
wally-0.0.20 features/push_features.feature