Sha256: 8423b715dcb552029c2e06ecc62c577436254959b7da782008d4abca310d3465

Contents?: true

Size: 1004 Bytes

Versions: 10

Compression:

Stored size: 1004 Bytes

Contents

Feature: prodder init

  Background:
    Given a prodder config in "prodder.yml" with project: blog
    And a "blog" git repository

  Scenario: Clone a project
    When I run `prodder init -c prodder.yml`
    Then the exit status should be 0
    And a directory named "prodder-workspace/blog" should exist
    And the workspace file "blog/README" should match /Read me/

  Scenario: Update pre-existing repository on re-initializing
    Given I run `prodder init -c prodder.yml`
    And a new commit is already in the "blog" git repository
    When I run `prodder init -c prodder.yml`
    Then the new commit should be in the workspace copy of the "blog" repository

  Scenario: Can't clone repository (no such repo, permissions, whatever)
    Given I deleted the "blog" git repository
    When I run `prodder init -c prodder.yml`
    Then the exit status should be 1
    And the output should contain "Failed to run 'git clone ./repos/blog"
    And the output should match /repository.*does not exist/

Version data entries

10 entries across 10 versions & 1 rubygems

Version Path
prodder-1.8.2 features/init.feature
prodder-1.8.1 features/init.feature
prodder-1.7.7 features/init.feature
prodder-1.7.6 features/init.feature
prodder-1.7.5 features/init.feature
prodder-1.7.4 features/init.feature
prodder-1.7.3 features/init.feature
prodder-1.7.2 features/init.feature
prodder-1.7.1 features/init.feature
prodder-1.7 features/init.feature