Logo: Relish

  1. Sign in

Project: relish

Private projects

Relish isn't just for open source projects. We want any teams who use Cucumber for their
proprietary applications to be able to share features amongst themselves using Relish
without worrying about other people seeing them.

Scenarios
Visitor looks at the projects for a user with a mix of public and private projects
Given
there is a publisher
And
the publisher has two projects, "foo" and "bar"
And
the visibility of project "bar" is private
When
I go to the page for the publisher
Then
I should see "foo"
But
I should not see "bar"
Visitor tries to access a private project directly
Given
there is a private project
When
I try to visit the page for the project
Then
I should be asked to sign in
Visitor tries to access a private project's features directly
Given
there is a private project
And
the project has a feature
When
I try to visit the page for the feature
Then
I should be asked to sign in
Visitor tries to access a private project, signs in as a user who's a collaborator
Given
there is a private project created by "[email protected]/password"
When
I try to visit the page for the project
And
I sign in as "[email protected]/password"
Then
I should be on the page for the project
Visitor tries to access a private project, signs in as a user who's not a collaborator
Given
there is a private project created by "[email protected]/password"
And
a user "[email protected]/password"
When
I try to visit the page for the project
And
I sign in as "[email protected]/password"
Then
I should be on the dashboard page

Last published over 6 years ago by mattwynne.