Do the blue touches in the properties of the cucumber highlight the usually missed ones?

Question

I realized that the blue strokes in the feature release mean that the step was skipped because something failed, but in all of my circuit scripts, I get the blue strokes, as well as a line that says that everything went.

Here is my outline of the script.

Scenario Outline: Attempt to assign a role when not authorized Given a <user_who_can_not_assign_roles> exists with email: " [e-mail] " And that user is signed in And I am on the user show page And a role exists with name: "<other_role1>" And a role exists with name: "<other_role2>" When I follow "Edit" Then I should not see "Admin" And I should not see "Manager" And I should not see "Salesperson" When I fill in "username" with "spuds" And I fill in "password" with "potatoes" And I fill in "password confirmation" with "potatoes" And I fill in "email" with " [e-mail] " And I press "Save" Then I should see "success" And a role should exist with name: "<other_role1>" And that role should not be one of the user roles And a role should exist with name: "<other_role2>" And that role should not be one of the user roles Examples: | user_who_can_not_assign_roles | other_role1 | other_role2 | | manager | Admin | Salesperson | | salesperson | Admin | Manager | 

When I run this function, I get this output.

-------------------......

2 scenarios (2 completed)
38 steps (38 passed)
0m3.300s

I get that these are two scenarios because I have 2 examples listed and 38 steps will be 19 times in a row. What I don’t understand is why he shows the blue strokes (as it usually shows the missing steps), when he also talks about 38 steps.

I would suggest that this is intended to be contours, because if I change the steps marked with a blue dash, this will seem unsuccessful. I was just looking for confirmation in the documents of the cucumber, and I can not find anything.

I am running rails 3.0.0, cucumber 0.9.3 and pickle 0.4.2.

Answer 1

The blue strokes in this case represent an analysis of the syntax of the script, which has more metadata than the test. I find this confusing. To better understand what is going on, try:

 cucumber -f pretty <your_fancy_scenario.feature> 

This will cause the cucumber to display the actual text of the script with color coding, not just dots and dashes.

Hope this helps!