To add a collaborator to this project you will need to use the Relish gem to add the collaborator via a terminal command. Soon you'll be able to also add collaborators here!
More about adding a collaboratorPush to a project
The relish gem provides a way for users to push their features folder to
a project on relishapp's servers for rendering.
- Background
-
- Given
- I have authenticated my user account via the console
- And
- a project "rspec/rspec-core"
- And
- I am a collaborator on the project "rspec-core"
- Scenarios
-
- A project with a single feature file containing a single scenario
- A project with a single feature file within a directory
- A project version with a single feature file containing a single scenario
- Attempt to push to a project to which you don't have rights
- Push to a private project
- Using the wrong case for the project name
- Specifying no project
- A project with a single feature file containing a single scenario
-
- Given
-
a file named "features/one.feature" with:
Feature: First Feature Scenario: First Scenario Given this is cool - When
-
I successfully run
relish push rspec/rspec-core - And
- I wait until all the jobs have run
- When
- I go to rspec-core's project page
- Then
- I should see "First Feature"
- When
- I follow the left-nav link to "First Feature"
- Then
- I should see "First Scenario"
- And
- I should see "Given this is cool"
- A project with a single feature file within a directory
-
- Given
-
a file named "features/directory/one.feature" with:
Feature: First Feature Scenario: First Scenario - When
-
I successfully run
relish push rspec/rspec-core - And
- I wait until all the jobs have run
- When
- I go to rspec-core's project page
- Then
- I should see "Directory"
- When
- I follow the left-nav link to "Directory"
- Then
- I should see "First Feature"
- When
- I follow the left-nav link to "First Feature"
- Then
- I should see "First Scenario"
- A project version with a single feature file containing a single scenario
-
- Given
- project "rspec-core" has a version named "2.0"
- Given
-
a file named "features/one.feature" with:
Feature: Version Feature Scenario: First Scenario - When
-
I successfully run
relish push rspec/rspec-core:2.0 - And
- I wait until all the jobs have run
- When
- I go to rspec's publisher page
- Then
- I should see "2.0"
- When
- I follow the left-nav link to version "2.0"
- Then
- I should be shown the default topic for rspec-core version 2.0
- And
- I should see "Version Feature"
- Attempt to push to a project to which you don't have rights
-
- Given
- I am not a collaborator on the "rspec-core" project
- And
-
a file named "features/one.feature" with:
Feature: One Scenario: One - When
-
I run
relish push rspec/rspec-core - Then
-
it should fail with:
Authorization failed
- Push to a private project
-
- Given
- the visibility of project "rspec-core" is private
- And
-
a file named "features/one.feature" with:
Feature: One Scenario: One - When
-
I run
relish push rspec/rspec-core - Then
-
it should pass with:
sent: features/one.feature
- Using the wrong case for the project name
-
- Given
-
a file named "features/one.feature" with:
Feature: First Feature - When
-
I run
relish push RSPEC/RSPEC-CORE - Then
-
it should fail with:
Project 'RSPEC/RSPEC-CORE' not found
- Specifying no project
-
- When
-
I run
relish push - Then
-
it should fail with:
Please specify a project. Run 'relish help' for usage information.
Last published almost 4 years ago by mattwynne.