Sha256: 0c66637362657d5ce309b4c657a0eb3e2c658c06d8cb8b0a5847472c093f2b29

Contents?: true

Size: 815 Bytes

Versions: 4

Compression:

Stored size: 815 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 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 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 see the uploaded feature

Version data entries

4 entries across 4 versions & 1 rubygems

Version Path
wally-0.0.44 features/push_features.feature
wally-0.0.43 features/push_features.feature
wally-0.0.42 features/push_features.feature
wally-0.0.41 features/push_features.feature