Skip to content

Instantly share code, notes, and snippets.

@chrisdarroch
Created July 13, 2010 22:49
Show Gist options
  • Save chrisdarroch/474676 to your computer and use it in GitHub Desktop.
Save chrisdarroch/474676 to your computer and use it in GitHub Desktop.
Feature: Application live validations
I want validation errors to appear as soon as they can be
In order to give feedback to the user as quickly as possible
Background: # features/application_live_validations.feature:5
Given a user exists with email: "[email protected]", first_name: "Test", last_name: "Man" # features/step_definitions/pickle_steps.rb:4
[2010-07-14 08:38:38] INFO WEBrick 1.3.1
[2010-07-14 08:38:38] INFO ruby 1.8.7 (2009-06-12) [universal-darwin10.0]
[2010-07-14 08:38:38] INFO WEBrick::HTTPServer#start: pid=47066 port=9887
And I log in as that user # features/step_definitions/user_steps.rb:21
And that user has started a FairGo application with one applicant # features/step_definitions/fairgo_steps.rb:15
And they have agreed to the privacy policy # features/step_definitions/fairgo_steps.rb:39
@javascript @wip
Scenario: Required fields indicate they can't be left blank # features/application_live_validations.feature:12
When I follow "Personal Details" # features/step_definitions/web_steps.rb:33
Then I should not see an inline error for the formtastic field "Full Name" # features/step_definitions/validation_steps.rb:82
expected #has_no_xpath?(#<Capybara::XPath:0x10ecef540 @paths=["//p[contains(concat(' ', @class, ' '), ' inline-errors ')]"]>) to return true, got false (Spec::Expectations::ExpectationNotMetError)
./features/step_definitions/validation_steps.rb:101
./features/step_definitions/validation_steps.rb:97
./features/step_definitions/web_steps.rb:14:in `with_scope'
./features/step_definitions/validation_steps.rb:83:in `/^I should not see an inline error for the formtastic field "([^"]*)"(?: within "([^\"]*)")?$/'
features/application_live_validations.feature:14:in `Then I should not see an inline error for the formtastic field "Full Name"'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment