Rails%203%20In%20Action

Adding more tags
cannot fill in, no text field, text area or password
field with id, name, or label 'Tags' found
You can fix this by taking these lines from app/views/tickets/_form.html.erb and moving
them into a new partial at app/views/tags/_form.html.erb:
Replace the code you removed from app/views/tickets/_form.html.erb with this line:
This new line will render your new tags partial. In order to make the failing step in
your scenario now pass, you re-use this same line inside the authorized? block inside
app/views/comments/_form.html.erb underneath the code you use to render the
State select box.
When you run bin/cucumber features/creating_comments.feature:47, you see
that this step is indeed passing, but now it’s the final step of your scenario that is failing:
Then I should see "bug" within "#ticket #tags"
expected there to be content "bug" in ""
This feature is not seeing the word “bug” within the content for the ticket’s tags
(which is empty), and so the scenario fails. This is because the code to associate a tag
with a ticket isn’t in the create action of CommentsController yet. In the create
action in TicketsController, you use this line to tag the ticket that was created:
@ticket.tag!(params[:tags])
You can use this same method to tag a comment’s ticket. On the line immediately
after if @comment.save in the create action inside CommentsController, you re-use
the tag! line. That’s all you need to get this scenario to pass, right? Run bin/cucumber
features/creating_comments.feature:47 to find out:
1 scenario (1 passed)
15 steps (15 passed)
Boom, that’s passing! Good stuff. Now for the cleanup. Make sure you haven’t broken
anything else by running rake cucumber:ok spec:
55 scenarios (55 passed)
598 steps (598 passed)
# and
27 examples, 1 failure, 10 pending
It would seem your spec/controllers/comments_controller_spec.rb doesn’t want to
play nice.
293