Sha256: 72ce936c7486443fc2f7b68880ab866df1a20a5d21f7f21ff8523faa8f8c9b30

Contents?: true

Size: 998 Bytes

Versions: 5

Compression:

Stored size: 998 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 "remote rejected"

  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.8.2 features/push.feature
prodder-1.8.1 features/push.feature
prodder-1.7.7 features/push.feature
prodder-1.7.6 features/push.feature
prodder-1.7.5 features/push.feature