Created
September 8, 2010 01:10
-
-
Save jdee/569424 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Failing Scenarios: | |
cucumber -p enhanced features/enhanced/attachments.feature:7 # Scenario: Delete an attachment from the add attachment screen | |
cucumber -p enhanced features/enhanced/attachments.feature:18 # Scenario: Delete an attachment from the event show screen | |
cucumber -p enhanced features/enhanced/cmr_filter_list.feature:7 # Scenario: Filtering the CMR list by one disease | |
cucumber -p enhanced features/enhanced/cmr_filter_list.feature:22 # Scenario: Filtering the CMR list by multiple diseases | |
cucumber -p enhanced features/enhanced/common_test_type_delete.feature:24 # Scenario: Deleting a common test type from show mode | |
cucumber -p enhanced features/enhanced/common_test_type_delete.feature:35 # Scenario: Deleting a common test type referenced by a lab result | |
cucumber -p enhanced features/enhanced/contact_fields_help_text.feature:7 # Scenario: Viewing contact event help text | |
cucumber -p enhanced features/enhanced/event_clinicians.feature:6 # Scenario: Adding and removing clinicians in new mode | |
cucumber -p enhanced features/enhanced/event_clinicians.feature:25 # Scenario: Adding clinicians in edit mode | |
cucumber -p enhanced features/enhanced/event_clinicians.feature:36 # Scenario: Clinician search should not include deleted clinicians | |
cucumber -p enhanced features/enhanced/event_contacts.feature:6 # Scenario: Adding and removing contacts in new mode | |
cucumber -p enhanced features/enhanced/event_contacts.feature:25 # Scenario: Adding contacts in edit mode | |
cucumber -p enhanced features/enhanced/event_diagnosing_facilities.feature:6 # Scenario: Adding and removing diagnosing facilities in new mode | |
cucumber -p enhanced features/enhanced/event_diagnosing_facilities.feature:24 # Scenario: Adding diagnosing facilities in edit mode | |
cucumber -p enhanced features/enhanced/event_diagnosing_facilities.feature:38 # Scenario: Adding and removing diagnosing facilities for a contact | |
cucumber -p enhanced features/enhanced/event_notes.feature:7 # Scenario: Event creation generates a note | |
cucumber -p enhanced features/enhanced/event_notes.feature:16 # Scenario: Adding a clinical note | |
cucumber -p enhanced features/enhanced/event_notes.feature:26 # Scenario: Adding an administrative note | |
cucumber -p enhanced features/enhanced/event_place_exposures.feature:7 # Scenario: Adding and removing place exposures in new mode | |
cucumber -p enhanced features/enhanced/event_place_exposures.feature:27 # Scenario: Adding and removing place exposures in edit mode | |
cucumber -p enhanced features/enhanced/event_place_exposures.feature:43 # Scenario: Adding two new place exposures at once | |
cucumber -p enhanced features/enhanced/event_place_exposures.feature:52 # Scenario: Editing a place exposure as a place event | |
cucumber -p enhanced features/enhanced/event_reporting_agency.feature:6 # Scenario: Adding and removing existing reporting agencies in new mode | |
cucumber -p enhanced features/enhanced/event_reporting_agency.feature:19 # Scenario: Adding and removing existing reporting agencies in edit mode | |
cucumber -p enhanced features/enhanced/fb_contact_core_field_configs.feature:6 # Scenario: Contact event core field configs | |
cucumber -p enhanced features/enhanced/fb_contact_core_follow_ups.feature:6 # Scenario: Contact event core follow ups | |
cucumber -p enhanced features/enhanced/fb_contact_core_view_configs.feature:6 # Scenario: Contact event core view configs | |
cucumber -p enhanced features/enhanced/fb_delete_library_elements.feature:7 # Scenario: Delete a question from the library | |
cucumber -p enhanced features/enhanced/fb_delete_library_elements.feature:17 # Scenario: Delete a grouped question from the library | |
cucumber -p enhanced features/enhanced/fb_delete_library_elements.feature:27 # Scenario: Delete a value set from the library | |
cucumber -p enhanced features/enhanced/fb_delete_library_elements.feature:42 # Scenario: Delete a grouped value set from the library | |
cucumber -p enhanced features/enhanced/fb_delete_library_elements.feature:58 # Scenario: Delete a group and its questions from the library | |
cucumber -p enhanced features/enhanced/fb_delete_library_elements.feature:69 # Scenario: Delete a group and its value sets from the library | |
cucumber -p enhanced features/enhanced/fb_morb_core_field_configs.feature:6 # Scenario: Morbidity event core field configs | |
cucumber -p enhanced features/enhanced/fb_morb_core_follow_ups.feature:6 # Scenario: Morbidity event core follow ups | |
cucumber -p enhanced features/enhanced/fb_morb_core_view_configs.feature:6 # Scenario: Morbidity event core view configs | |
cucumber -p enhanced features/enhanced/fb_place_core_field_configs.feature:6 # Scenario: Place event core field configs | |
cucumber -p enhanced features/enhanced/fb_place_core_follow_ups.feature:7 # Scenario: Place event core follow ups | |
cucumber -p enhanced features/enhanced/fb_place_core_view_configs.feature:6 # Scenario: Place event core view configs | |
cucumber -p enhanced features/enhanced/fb_questions_have_unique_short_names.feature:8 # Scenario: Creating a new question without a short name | |
cucumber -p enhanced features/enhanced/fb_questions_have_unique_short_names.feature:16 # Scenario: Creating a new question with a short name | |
cucumber -p enhanced features/enhanced/fb_questions_have_unique_short_names.feature:24 # Scenario: Creating a new question with a short name that is already in use | |
cucumber -p enhanced features/enhanced/fb_questions_have_unique_short_names.feature:33 # Scenario: Editing a question to change its short name | |
cucumber -p enhanced features/enhanced/fb_questions_have_unique_short_names.feature:43 # Scenario: Trying to edit a question short name after publishing a form | |
cucumber -p enhanced features/enhanced/fb_questions_have_unique_short_names.feature:53 # Scenario: Trying to copy a question from the library that has a short name that is already in use | |
cucumber -p enhanced features/enhanced/fb_questions_have_unique_short_names.feature:63 # Scenario: Creating a new question on an already published form | |
cucumber -p enhanced features/enhanced/fb_value_codes.feature:6 # Scenario: Saving values | |
cucumber -p enhanced features/enhanced/loinc_code_admin_disable_organism.feature:7 # Scenario: Make a loinc code scale 'Nominal' | |
cucumber -p enhanced features/enhanced/loinc_code_admin_disable_organism.feature:26 # Scenario: Change a loinc code scale from 'Nominal' to 'Ordinal' | |
cucumber -p enhanced features/enhanced/morbidity_event_routing.feature:6 # Scenario: Reopening an event already received by the state. | |
cucumber -p enhanced features/enhanced/morbidity_fields_help_text.feature:7 # Scenario: Viewing morbidity event help text | |
cucumber -p enhanced features/enhanced/place_fields_help_text.feature:7 # Scenario: Viewing place event help text | |
cucumber -p enhanced features/enhanced/remove_form_from_event.feature:7 # Scenario: Morbidity event form removal as admin | |
cucumber -p enhanced features/enhanced/user_roles_management.feature:7 # Scenario: Add a role to a user | |
cucumber -p enhanced features/enhanced/user_roles_management.feature:23 # Scenario: Remove a role from a user | |
cucumber -p enhanced features/enhanced/user_roles_management.feature:38 # Scenario: Removing a new role w/out updating | |
cucumber -p enhanced vendor/trisano/trisano_outbreaks/features/enhanced/fb_outbreak_core_field_configs.feature:6 # Scenario: Outbreak event core field configs | |
cucumber -p enhanced vendor/trisano/trisano_outbreaks/features/enhanced/fb_outbreak_core_follow_ups.feature:6 # Scenario: Outbreak event core follow ups | |
cucumber -p enhanced vendor/trisano/trisano_outbreaks/features/enhanced/fb_outbreak_core_view_configs.feature:6 # Scenario: Outbreak event core view configs | |
cucumber -p enhanced vendor/trisano/trisano_patient_view/features/enhanced/patient_view_tabs.feature:3 # Scenario: Viewing a patient's demographic information | |
cucumber -p enhanced vendor/trisano/trisano_perinatal_hep_b/features/enhanced/editing_hep_b_fields.feature:7 # Scenario: Editing expected delivery data on a Hepatitis B Pregnancy Event | |
cucumber -p enhanced vendor/trisano/trisano_perinatal_hep_b/features/enhanced/editing_hep_b_fields.feature:23 # Scenario: Editing actual delivery data on a Hepatitis B Pregnancy Event | |
cucumber -p enhanced vendor/trisano/trisano_perinatal_hep_b/features/enhanced/editing_hep_b_fields.feature:42 # Scenario: Selecting an expected delivery facility on an event | |
cucumber -p enhanced vendor/trisano/trisano_perinatal_hep_b/features/enhanced/editing_hep_b_fields.feature:54 # Scenario: Selecting an actual delivery facility on an event | |
cucumber -p enhanced vendor/trisano/trisano_perinatal_hep_b/features/enhanced/editing_hep_b_fields.feature:66 # Scenario: Updating an actual delivery facility should not reset date | |
cucumber -p enhanced vendor/trisano/trisano_perinatal_hep_b/features/enhanced/editing_hep_b_fields.feature:80 # Scenario: Removing an actual delivery facility in the same session it was added | |
cucumber -p enhanced vendor/trisano/trisano_perinatal_hep_b/features/enhanced/generating_state_manager_tasks.feature:8 # Scenario: Completing expected delivery data | |
cucumber -p enhanced vendor/trisano/trisano_perinatal_hep_b/features/enhanced/generating_state_manager_tasks.feature:24 # Scenario: Completing expected delivery data by entering a new expected delivery facility | |
cucumber -p enhanced vendor/trisano/trisano_perinatal_hep_b/features/enhanced/hep_b_contact_treatment_fields.feature:3 # Scenario: Adding multiple contact treatments at one time | |
69 scenarios (69 failed) | |
708 steps (708 skipped) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment