Rails%203%20In%20Action

Tracking changes
Awesome! Now let’s try rerunning rake cucumber:ok spec. That should be the last
thing you need to fix. You should see the following output:
49 scenarios (49 passed)
515 steps (515 passed)
# and
33 examples, 0 failures, 16 pending
Excellent, everything’s fixed. Let’s commit these changes now:
git add .
git commit -m "When updating a comment's status, it also updates
➥the ticket's status"
git push
It’s great that you’ve now got the ticket status updating along with the comment status,
but it would be handy to know what the timeline of a status change looks like. You can
display this on the comment by showing a little indication of whether the state has
changed during that comment. Let’s work on adding this tidbit of information to the
comments right now.
10.3 Tracking changes
When a person posts a comment that changes the state of a ticket, you’d like this
information displayed on the page next to the comment, as shown in figure 10.10.
By visually tracking this state change, along with the text of the
comment, you can provide context as to why the state was changed.
At the moment, you only track the state of the comment and then
don’t even display it alongside the comment’s text; you only use it to
update the ticket’s status.
10.3.1 Ch-ch-changes
What you need now is some way of making sure that, when changing a ticket’s state by
way of a comment, the “State: Open” text appears. A scenario would fit this bill, and
luckily you wrote one that fits almost perfectly. This scenario is the final scenario
(“Changing a ticket’s state”) in features/creating_comments.feature.
To check for the state change text in your “Changing a ticket’s state” scenario, you
add this single line to the bottom of it:
Then I should see "State: Open" within "#comments"
If the ticket was assigned the New state, this text would say “State: New ?' Open,” but
because your tickets don’t have default states assigned to them the previous state for
the first comment will be nil. When you run this scenario by using bin/cucumber
features/creating_comments.feature:33, it will fail:
Then I should see "State: Open" within "#comments"
expected there to be content "State: Open"
in "\n \n user@ticketee.com (User)\n
This is a real issue\n\n"
263
Figure 10.10
State transitions