Rails%203%20In%20Action

308 CHAPTER 11 Tagging
This is because, like the tags parameter, you’re attempting to set a string value on a
field that is actually an association. You must take the state key out of the parameters
hash inside this step so that it is not parsed as a normal field of a ticket.
To fix this little issue, open features/step_definitions/ticket_steps.rb and change the
step definition to be this:
Given /^"([^\"]*)" has created a ticket for this project:$/ do |email, table|
table.hashes.each do |attributes|
tags = attributes.delete("tags")
state = attributes.delete("state")
ticket = @project.tickets.create!(
attributes.merge!(:user =>
User.find_by_email!(email)))
ticket.state = State.find_or_create_by_name(state) if state
ticket.tag!(tags) if tags
ticket.save
end
end
On the second line of this step definition, you remove the state key from the
attributes hash, using the delete method again. On the second-to-last line you
assign the ticket’s state, but only if there was a state defined from attributes. The
ticket would be saved if you had specified a tag in the attributes, but if you didn’t then
you need to call save again, as you do on the final line of this step definition.
With all the Background fiddling done, you can add a scenario that searches for
tickets with a given state. It goes like this:
Scenario: Finding by state
When I fill in "Search" with "state:Open"
And I press "Search"
Then I should see "Tag!"
And I should not see "Tagged!"
This should show any ticket with the open state, and hide all other tickets. When you
run this feature with bin/cucumber features/searching.feature, you see that this is
not the case. It can still see the Tagged! ticket:
And I should not see "Tagged!"
Failed assertion, no message given. (MiniTest::Assertion)
When a user performs a search on only an undefined label (such as your state label),
Searcher will return all the records for that table. This is the behavior you are seeing
right now, so it means that you need to define your state label in your model. Let’s
open app/models/ticket.rb and add this line to your searcher block:
label :state, :from => :state, :field => "name"
With this label defined, your newest scenario will now pass when you re-run bin/
cucumber features/searching.feature:
2 scenarios (2 passed)
26 steps (26 passed)