Sha256: d2f6b055ef087da83c8918db1c42204fb4d016f9c932b7c9d4d21bd18e44f6ce

Contents?: true

Size: 1006 Bytes

Versions: 5

Compression:

Stored size: 1006 Bytes

Contents

Feature: prodder push

  Background:
    Given a prodder config in "prodder.yml" with project: blog
    And a "blog" git repository
    And I successfully run `prodder init -c prodder.yml`
    And I successfully run `prodder dump -c prodder.yml`
    And I successfully run `prodder commit -c prodder.yml`

  Scenario: Changes are pushed upstream
    When I successfully run `prodder push -c prodder.yml`
    Then the exit status should be 0
    Then the new commit should be in the remote repository

  Scenario: Push fails due to permissions
    Given the "blog" git repository does not allow pushing to it
    When I run `prodder push -c prodder.yml`
    Then the exit status should be 1
    And the output should contain "insufficient permission"

  Scenario: Push fails due to non-fast-forward
    Given a new commit is already in the "blog" git repository
    When I run `prodder push -c prodder.yml`
    Then the exit status should be 1
    And the output should contain "Refusing to push to remote"

Version data entries

5 entries across 5 versions & 1 rubygems

Version Path
prodder-1.7.4 features/push.feature
prodder-1.7.3 features/push.feature
prodder-1.7.2 features/push.feature
prodder-1.7.1 features/push.feature
prodder-1.7 features/push.feature