Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Fetching contributors…

Cannot retrieve contributors at this time

127 lines (112 sloc) 5.381 kb
Feature: Lighthouse integration
In order pull in potential features from lighthouse
As the system
I want to be able to retrieve a list of features
Scenario: We should be able to talk to lighthouse
Given we are using the account name "baphled"
And we have an the project number "50164"
When we specify the ticket type "state:open tagged:feature"
When we retrieve tickets
Scenario: We need a place to edit our lighthouse resource information
Given I visit the parking page
When I use the "New Resource information" link
Then I should be sent to the "New Resource" page
Scenario: We want to be able to add a new lighthouse resource
Given we visit the new parking page
When I fill in "resource_name" with "baphled"
And I fill in "resource_project_id" with "50164"
Then submit the form
And the resource information should be saved
Scenario: We should be able to use the lighthouse resource when it has been stored
Given we have set up the lighthouse resource
And I visit the parking page
When I select "baphled" from "resource_id"
And I fill in "parking_tag" with "feature"
And submit the form
And there should be a list of tickets found
Scenario: We should be able to import all found tickets into the parking area.
Given we have set up the lighthouse resource
And I visit the parking page
When I select "baphled" from "resource_id"
And I fill in "parking_tag" with "feature"
And submit the form
Then I should be able to select tickets to add to parking
Scenario: We should display all parked tickets on the index page
Given we have set up the lighthouse resource
And there are parked tickets on the system
When I visit the parking page
Then a list of parked ticket should be displayed
Scenario: We need to be able to save the selected tickets and save them as parked item
Given we have set up the lighthouse resource
And I visit the parking page
When I select "baphled" from "resource_id"
And I fill in "parking_tag" with "feature"
And submit the form
Then I should be able to select tickets to add to parking
# Need to refactor so that we have a stubbed version of this ticket, will break once ticket is closed
When I check "lighthouse[ticket_id][]"
And I press "Park"
Then one item should be saved as parked items
Scenario: We should not be able to save a ticket if the ticket and the body are already in the system
Given we have set up the lighthouse resource
And we have a tickets that is invalid
And I visit the parking page
When I select "baphled" from "resource_id"
And I fill in "parking_tag" with "feature"
And submit the form
# Need to refactor so that we have a stubbed version of this ticket, will break once ticket is closed
When I check "lighthouse[ticket_id][]"
And I press "Park"
Then the flash message "Unable to save tickets" should be displayed
Scenario: We should not save any tickets if one of them is invalid
Given we have set up the lighthouse resource
And there are no tickets parked
And I visit the parking page
When I select "baphled" from "resource_id"
And I fill in "parking_tag" with "feature"
And submit the form
Then I should be able to select tickets to add to parking
And I should not see a list of tickets to import
Scenario: We should be able to view a tickets description body
Given we have set up the lighthouse resource
And there are no tickets parked
And I visit the parking page
When I select "baphled" from "resource_id"
And I fill in "parking_tag" with "feature"
And submit the form
And I check "lighthouse[ticket_id][]"
And I press "Park"
Then the save tickets should have a body
Scenario: A user should not be able to import tickets if a resource has not been set up
Given there are no resources
When I visit the parking page
Then the ticket search form should not be visible.
Scenario: We should be able to view a tickets title
Given we have set up the lighthouse resource
And there are no tickets parked
And I visit the parking page
When I select "baphled" from "resource_id"
And I fill in "parking_tag" with "feature"
And submit the form
And I check "lighthouse[ticket_id][]"
And I press "Park"
Then the saved tickets should have a title
Scenario: We should be able to select a parked ticket and convert in into a feature
Given we are using the account name "baphled"
And we have an the project number "50164"
And there are are tickets
When I visit the parking page
And we click on the first ticket
Then the feature form should be displayed
Scenario: The project name must be valid
Given we visit the new parking page
When I fill in "resource_name" with "foo"
When I fill in "resource_project_id" with "50164"
And submit the form
Then there a error "Must be a valid LightHouse project name" should be displayed
Scenario: The project number must be valid
Given we visit the new parking page
When I fill in "resource_name" with "baphled"
When I fill in "resource_project_id" with "23"
When submit the form
Then there a error "Must be a valid LightHouse project id" should be displayed
Jump to Line
Something went wrong with that request. Please try again.