diaspora/features/signs_up.feature
Jonne Haß 300752fc87 bump capybara
* removed wait_until where possible
* replaced wait_until with DOM obersavtions
* added match: :first to all finders that assumed getting the first element
* replaced evaluate_script with execute_script where possible
* replaced a few execute_script with DOM observations through Capybara
* removed sleep where possible
* replaced sleep with DOM obersvations
* replaced "wait for ajax" with DOM obersavations
* replaced alert confirmation with new selenium API
* bump selenium webdriver
* made any other fixes to get green again
2013-07-31 01:47:23 +02:00

72 lines
2.5 KiB
Gherkin

@javascript
Feature: new user registration
Background:
When I go to the new user registration page
And I fill in the following:
| user_username | ohai |
| user_email | ohai@example.com |
| user_password | secret |
| user_password_confirmation | secret |
And I press "Continue"
Then I should be on the getting started page
And I should see "Well, hello there!" and "Who are you?" and "What are you into?"
Scenario: new user goes through the setup wizard
When I fill in the following:
| profile_first_name | O |
And I follow "awesome_button"
And I confirm the alert
Then I should be on the stream page
And I should not see "awesome_button"
Scenario: new user does not add any tags in setup wizard and cancel the alert
When I fill in the following:
| profile_first_name | some name |
And I follow "awesome_button"
And I reject the alert
Then I should be on the getting started page
And I should see a flash message containing "Alright, I'll wait."
Scenario: new user skips the setup wizard
When I follow "awesome_button"
And I confirm the alert
Then I should be on the stream page
Scenario: closing a popover clears getting started
When I follow "awesome_button"
And I confirm the alert
Then I should be on the stream page
And I have turned off jQuery effects
And I wait for the popovers to appear
And I click close on all the popovers
And I go to the home page
Then I should not see "Welcome to Diaspora"
Scenario: user fills in bogus data - client side validation
When I log out manually
And I go to the new user registration page
And I fill in the following:
| user_username | $%&(/&%$&/=)(/ |
And I press "Continue"
Then following fields should have validation errors:
| user_username |
| user_email |
| user_password |
When I fill in the following:
| user_username | valid_user |
| user_email | this is not a valid email $%&/()( |
And I press "Continue"
Then following fields should have validation errors:
| user_email |
| user_password |
When I fill in the following:
| user_email | valid@email.com |
| user_password | 1 |
And I press "Continue"
Then following field should have validation error:
| user_password |