Sha256: e67ce8a9d55eea4a20485344cc526b81970a0d1ef1d5f5db3b1c4bb83b6c6f2f
Contents?: true
Size: 1.55 KB
Versions: 1
Compression:
Stored size: 1.55 KB
Contents
@api_server @announce Feature: Developer starts pairzone Scenario: Given I have a local git repository When "bob" runs "pairzone start" in test mode Then a new pairzone is started for "bob" And the code in my current directory is pushed to the server And an SSH connection is made to my new pairzone And the code is downloaded to a "pairzone" branch when I quit the session Scenario: Developer starts pairzone in the background Given I have a local git repository When "bob" runs "pairzone start --background" in test mode Then a new pairzone is started for "bob" in the background Scenario: Developer rejoins previously started pairzone Given I have a local git repository When "bob" runs "pairzone start --background" in test mode And "bob" runs "pairzone start" in test mode Then "bob" should be connected to "bob-aruba" Scenario: Developer adds collaborator Given I have a local git repository When "bob" runs "pairzone start -c derek" in test mode Then "derek" is added as a collaborator on my new pairzone When "bob" runs "pairzone start -c derek,jim" in test mode Then "derek" is added as a collaborator on my new pairzone And "jim" is added as a collaborator on my new pairzone Scenario: Developer adds non-existent collaborator Given I have a local git repository When "bob" runs "pairzone start -c derek,invalid_collaborator" in test mode Then "derek" is added as a collaborator on my new pairzone And "invalid_collaborator" is not added as a collaborator on my new pairzone
Version data entries
1 entries across 1 versions & 1 rubygems
Version | Path |
---|---|
pairzone-0.0.1 | features/developer_starts_pairzone.feature |