Skip to content

Commit

Permalink
Added a few more scenarios for selecting all tickets to be imported a…
Browse files Browse the repository at this point in the history
…s well as storing a tickets title (which we'll use to populate our parked feature).
  • Loading branch information
baphled committed May 24, 2010
1 parent 364d955 commit f3b532e
Showing 1 changed file with 22 additions and 1 deletion.
23 changes: 22 additions & 1 deletion features/plain/lighthouse_integration.feature
Original file line number Diff line number Diff line change
Expand Up @@ -94,6 +94,17 @@ Feature: Lighthouse integration
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 have set up the lighthouse resource
And there are no tickets parked
Expand All @@ -104,4 +115,14 @@ Feature: Lighthouse integration
And I check "lighthouse[ticket_id][]"
And I press "Park"
When we click on the first ticket
Then the feature form should be populated with the ticket information
Then the feature form should be populated with the ticket information

Scenario: We importing tickets we should be able to select all tickets for import
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 "select-all"
Then all tickets should be selected

0 comments on commit f3b532e

Please sign in to comment.