Sha256: dfa122878bb87fbdac78c8c49c7b9d08190f742af830d1b9f15e45d530a92732

Contents?: true

Size: 836 Bytes

Versions: 7

Compression:

Stored size: 836 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 /my_project_name/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 /my_project_name/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 /my_project_name/features with the authentication code
    And I visit "my_project_name" page
    Then I should see the uploaded feature

Version data entries

7 entries across 7 versions & 1 rubygems

Version Path
wally-0.0.40 features/push_features.feature
wally-0.0.39 features/push_features.feature
wally-0.0.38 features/push_features.feature
wally-0.0.37 features/push_features.feature
wally-0.0.36 features/push_features.feature
wally-0.0.35 features/push_features.feature
wally-0.0.34 features/push_features.feature