student_search.feature

Scenario: Student can search for a user
    Given I am viewing the user list
      And I have entered the search term "cwl15"
     When I press search
     Then I will see the following search results:
        | cwl15 |

@javascript
Scenario: Student will be suggested search terms to help speed up their search
    Given I am viewing the user list
     When I enter the search term "cwl"
     Then I will see the following search term suggestions:
      | cwl12 |
      | cwl13 |
      | cwl14 |

Scenario: User is given the option the search across different facets
    Given I am viewing the user list
     Then I will see the following checkboxes on the search form:
      | first name |
      | last name  |
      | email      |



# If you aim to capture the intention behind the scenario, then imo it's becomes
# clearer how much 'testing' that scenario needs to do.
# Here adding other checkboxes wouldn't add anything to the scenario.
# Also from a `test/coverage` perspective it probably covers a large area of the 
# underlying implementation, if not just ensuring that all the code is stitched together correctly.
# You can then implement unit level tests to cover the various iterations of this, ie. the different checkboxes.

Scenario: Student can search within facets to make their search more accurate
    Given I am viewing the user list
      And I have selected the "group_name" checkbox
     When I enter the search term "cwl" and press search
     Then I will see the following search results:
          | ?? |