Sha256: d6fa1b1baa0b7b30b66d5502d354b4dfe89df08ec860d2739379163359d1ec52
Contents?: true
Size: 1.57 KB
Versions: 15
Compression:
Stored size: 1.57 KB
Contents
Feature: Sign in
In order to get access to protected sections of the site
A user
Should be able to sign in
Scenario: User is not signed up
Given no user exists with an email of "email@person.com"
When I go to the sign in page
And I sign in as "email@person.com/password"
Then I should see "Bad email or password"
And I should not be signed in
Scenario: User is not confirmed
Given I signed up with "email@person.com/password"
When I go to the sign in page
And I sign in as "email@person.com/password"
Then I should see "User has not confirmed email"
And I should not be signed in
Scenario: User enters wrong password
Given I am signed up and confirmed as "email@person.com/password"
When I go to the sign in page
And I sign in as "email@person.com/wrongpassword"
Then I should see "Bad email or password"
And I should not be signed in
Scenario: User signs in successfully
Given I am signed up and confirmed as "email@person.com/password"
When I go to the sign in page
And I sign in as "email@person.com/password"
Then I should see "Signed in successfully"
And I should be signed in
Scenario: User signs in and checks "remember me"
Given I am signed up and confirmed as "email@person.com/password"
When I go to the sign in page
And I sign in with "remember me" as "email@person.com/password"
Then I should see "Signed in successfully"
And I should be signed in
When I return next time
Then I should be signed in
Version data entries
15 entries across 15 versions & 4 rubygems