bmorris@cincinnatus:~/Projects/importal/apps/consumer_direct/consumer_direct_web_site$ RAILS_ENV=integration rake cucumber
NOTICE: running consumer direct common v 0.2.1
/home/bmorris/.rvm/rubies/ruby-1.8.7-p334/bin/ruby -S bundle exec cucumber  --profile default
Using the default profile...
NOTICE: running consumer direct common v 0.2.1
Feature: Adding a beneficiary

  Background:                                    # features/beneficiaries.feature:3
    Given a beneficiary relationship of "Spouse" # features/step_definitions/beneficiary_steps.rb:1
    And a beneficiary relationship of "Wife"     # features/step_definitions/beneficiary_steps.rb:1

  Scenario: Adding a Person beneficiary               # features/beneficiaries.feature:7
    Given There is one case                           # features/step_definitions/consumer_direct_cases.rb:9
    When I begin to add a beneficiary                 # features/step_definitions/beneficiary_steps.rb:60
    And I enter "Bobby" for first name                # features/step_definitions/beneficiary_steps.rb:7
    And I enter "Tables" for last name                # features/step_definitions/beneficiary_steps.rb:11
    And I enter "Spouse" for beneficiary relationship # features/step_definitions/beneficiary_steps.rb:26
    When I click "Add"                                # features/step_definitions/beneficiary_steps.rb:31
    Then a beneficiary has been added                 # features/step_definitions/beneficiary_steps.rb:68
    And the beneficiary first name is "Bobby"         # features/step_definitions/beneficiary_steps.rb:38
    And the beneficiary last name is "Tables"         # features/step_definitions/beneficiary_steps.rb:42
    And the beneficiary relationship is "Spouse"      # features/step_definitions/beneficiary_steps.rb:54

  Scenario: Cancel adding a beneficiary          # features/beneficiaries.feature:32
    Given There is one case                      # features/step_definitions/consumer_direct_cases.rb:9
    And I have one beneficiary                   # features/step_definitions/beneficiary_steps.rb:111
    When I begin to add a beneficiary            # features/step_definitions/beneficiary_steps.rb:60
    And I enter "Bobby" for first name           # features/step_definitions/beneficiary_steps.rb:7
    And I enter "Tables" for last name           # features/step_definitions/beneficiary_steps.rb:11
    When I click "Cancel"                        # features/step_definitions/beneficiary_steps.rb:31
    Then the "first_name" field should be empty  # features/step_definitions/beneficiary_steps.rb:103
    And the "last_name" field should be empty    # features/step_definitions/beneficiary_steps.rb:103

  # TODO - Uncomment this after refactoring to create beneficiaries controller
  # Scenario: Validations prevent adding a beneficiary
  #   Given There is one case
  #   When I begin to add a beneficiary
  #   And I click "Add"
  #   Then a beneficiary has not been added
  Scenario: Editing a beneficiary                                        # features/beneficiaries.feature:49
    Given There is one case                                              # features/step_definitions/consumer_direct_cases.rb:9
    And I have one beneficiary with the following attributes:            # features/step_definitions/beneficiary_steps.rb:78
      | first_name | last_name | beneficiary_relationship |
      | Bobby      | Tables    | Spouse                   |
    When I begin to edit the beneficiary                                 # features/step_definitions/beneficiary_steps.rb:85
    And I enter "Robert" for first name                                  # features/step_definitions/beneficiary_steps.rb:7
    And I enter "Vector" for last name                                   # features/step_definitions/beneficiary_steps.rb:11
    And I enter "Wife" for beneficiary relationship                      # features/step_definitions/beneficiary_steps.rb:26
    When I click "Update"                                                # features/step_definitions/beneficiary_steps.rb:31
    Then the beneficiary has been updated with the following attributes: # features/step_definitions/beneficiary_steps.rb:90
      | first_name | last_name | beneficiary_relationship |
      | Robert     | Vector    | Wife                     |

  Scenario: Deleting a beneficiary               # features/beneficiaries.feature:63
    Given There is one case                      # features/step_definitions/consumer_direct_cases.rb:9
    And I have one beneficiary                   # features/step_definitions/beneficiary_steps.rb:111
    When I am on beneficiary                     # features/step_definitions/web_steps.rb:36
    And I click delete beneficiary               # features/step_definitions/beneficiary_steps.rb:121
    Then the case has no beneficiaries           # features/step_definitions/beneficiary_steps.rb:116

  Scenario: Cancel editing a beneficiary         # features/beneficiaries.feature:70
    Given There is one case                      # features/step_definitions/consumer_direct_cases.rb:9
    And I have one beneficiary                   # features/step_definitions/beneficiary_steps.rb:111
    When I begin to edit the beneficiary         # features/step_definitions/beneficiary_steps.rb:85
    And I click "Cancel"                         # features/step_definitions/beneficiary_steps.rb:31
    Then I should see "Add"                      # features/step_definitions/web_steps.rb:58
    And I should not see "Update"                # features/step_definitions/web_steps.rb:66
    And the "first_name" field should be empty   # features/step_definitions/beneficiary_steps.rb:103
    And the "last_name" field should be empty    # features/step_definitions/beneficiary_steps.rb:103

Feature: Display the appropriate State Form Variations for Esig documents

  Background:                                                 # features/form_mappings.feature:3
    Given I have Form Mappings with the following attributes: # features/step_definitions/form_mapping_steps.rb:1
      | state_code | hipaa            | notices_of_information_practices | declaration_agreement_and_authorization |
      | IL         | illinois_hipaa   | illinois_notices                 | illinois_authorization                  |
      | CA         | california_hipaa | california_notices               | california_authorization                |
      Validation failed: State code has already been taken (ActiveRecord::RecordInvalid)
      ./features/step_definitions/form_mapping_steps.rb:3
      ./features/step_definitions/form_mapping_steps.rb:2:in `each'
      ./features/step_definitions/form_mapping_steps.rb:2:in `/^I have Form Mappings with the following attributes:$/'
      features/form_mappings.feature:4:in `Given I have Form Mappings with the following attributes:'

  Scenario: Displaying Illinois HIPAA Form                    # features/form_mappings.feature:9
    Given There is one case                                   # features/step_definitions/consumer_direct_cases.rb:9
    And the state applied is IL                               # features/step_definitions/form_mapping_steps.rb:7
    When I begin esig hipaa                                   # features/step_definitions/form_mapping_steps.rb:16
    Then I should see the image illinois_hipaa                # features/step_definitions/form_mapping_steps.rb:11

  Scenario: Displaying California Notice Form                 # features/form_mappings.feature:15
    Given There is one case                                   # features/step_definitions/consumer_direct_cases.rb:9
    And the state applied is CA                               # features/step_definitions/form_mapping_steps.rb:7
    When I begin esig notice                                  # features/step_definitions/form_mapping_steps.rb:16
    Then I should see the image california_notices            # features/step_definitions/form_mapping_steps.rb:11

  Scenario: Displaying Illinois History Form                  # features/form_mappings.feature:21
    Given There is one case                                   # features/step_definitions/consumer_direct_cases.rb:9
    And the state applied is IL                               # features/step_definitions/form_mapping_steps.rb:7
    When I begin esig history                                 # features/step_definitions/form_mapping_steps.rb:16
    Then I should see the image illinois_authorization        # features/step_definitions/form_mapping_steps.rb:11

Feature: Verifying the Applicant's Identity
  In order to verify an applicant's identity
  As Consumer Direct
  I want to query the LexisNexis Identity Risk Management API

Feature: Navigating Through a Case
  In order to fill out a case
  As a consumer
  I want to fill out all information and have it saved

  Scenario: Getting Started creates a case # features/navigate_through_application.feature:6
    Given I am on the home page            # features/step_definitions/web_steps.rb:36
    When I get started                     # features/step_definitions/navigation_steps.rb:37
    Then there should be "1" case          # features/step_definitions/consumer_direct_cases.rb:16

  Scenario: Fills out all 13 pages           # features/navigate_through_application.feature:11
    Given There are no cases                 # features/step_definitions/consumer_direct_cases.rb:5
HTTPI executes HTTP POST using the httpclient adapter
HTTPI executes HTTP POST using the httpclient adapter
HTTPI executes HTTP POST using the httpclient adapter
    When I fill out all of the pages         # features/step_definitions/navigation_steps.rb:5
    Then the data has been saved on the case # features/step_definitions/navigation_steps.rb:49

  Scenario: Followup is shown when hospitalization is answered yes   # features/navigate_through_application.feature:16
    Given There is one case                                          # features/step_definitions/consumer_direct_cases.rb:9
    When I answer "Yes" to the hospitalized question                 # features/step_definitions/navigation_steps.rb:19
    Then the case should be on the "health_follow_up_questions" page # features/step_definitions/navigation_steps.rb:55

  Scenario: Followup is not shown when hospitalization is answered no  # features/navigate_through_application.feature:21
    Given There is one case                                            # features/step_definitions/consumer_direct_cases.rb:9
    When I answer "No" to the hospitalized question                    # features/step_definitions/navigation_steps.rb:19
    Then the case should be on the "medical_generic_ko_questions" page # features/step_definitions/navigation_steps.rb:55

  Scenario: Followup answer is wiped out when hospitalization is changed from yes to no # features/navigate_through_application.feature:26
    Given There is one case                                                             # features/step_definitions/consumer_direct_cases.rb:9
    When I answer "Yes" to the hospitalized question                                    # features/step_definitions/navigation_steps.rb:19
    And I answer "Yes" to the health followup question                                  # features/step_definitions/navigation_steps.rb:29
    And I answer "No" to the hospitalized question                                      # features/step_definitions/navigation_steps.rb:19
    Then the case should not have a value for the health followup question              # features/step_definitions/navigation_steps.rb:59

Failing Scenarios:
cucumber features/form_mappings.feature:9 # Scenario: Displaying Illinois HIPAA Form

13 scenarios (1 failed, 2 skipped, 10 passed)
81 steps (1 failed, 14 skipped, 66 passed)
0m8.683s
rake aborted!
Command failed with status (1): [/home/bmorris/.rvm/rubies/ruby-1.8.7-p334/...]

Tasks: TOP => cucumber => cucumber:ok
(See full trace by running task with --trace)