Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scenarios using table showing up yellow in HTML output since 1.3.0 #493

Closed
fabrice31 opened this issue Jun 27, 2013 · 12 comments
Closed

Scenarios using table showing up yellow in HTML output since 1.3.0 #493

fabrice31 opened this issue Jun 27, 2013 · 12 comments
Assignees
Milestone

Comments

@fabrice31
Copy link

When you use a table in a scenario, the HTML output is showing in yellow.
(The console output is fine)

Example :

    Scenario: I test a table
       When I test data with:
       | name       | value       |
       | TheName | TheValue |

This issue happen only with version > 1.3.0

@mattwynne
Copy link
Member

Would you be interested in working on a patch? I'm working on code for version 2.0 of Cucumber that will replace this faulty code, so I'm not motivated to go back into this code and fix bugs in it. Until 2.0 is released though, I'm sure our users would be grateful if you managed to fix it.

@fabrice31
Copy link
Author

I tried, but I think I am not able to :(
The bug seems to come from this commit : cucumber/common@7dc7913
(the change of the formatter seems good, I don't know why it is wrong)
But when I unpack the gem and install it again, without any modification, it works again (I never did it before, I may do it wrong)

@ambirag
Copy link
Contributor

ambirag commented Jul 16, 2013

@mattwynne i'll see if i can fix this because its impacting us as well

@fabrice31 are you not seeing this anymore after you reinstalled the cucumber ?

@fabrice31
Copy link
Author

@ambirag update do 1.3.4, I am not seeing it anymore

@ambirag
Copy link
Contributor

ambirag commented Jul 17, 2013

@fabrice31 we are using 1.3.4 and only started seeing this issue after upgrading to cucumber 1.3.4
Any scenario / scenario outline that has an inline table marked in yellow even thought it has passed.

@fabrice31
Copy link
Author

@ambirag I had the opposit : a scenario that has inline table was always marked yellow, event though all has passed.

@fabrice31 fabrice31 reopened this Jul 17, 2013
@bpattonjr
Copy link

I agree with @fabrice31 that it comes from the 7dc7913 commit.

I was able to fix it by reverting just the check for status.nil? on line 405 of lib/cucumber/formatter/html.rb that was added in that commit. And removing the status.nil? check doesn't seem to break the intended fix for #337, although I did not run all tests.

@mattwynne
Copy link
Member

@os97673 can you take a look at this?

@os97673
Copy link
Member

os97673 commented Jul 29, 2013

@mattwynne sure, I will, as soon as will be back from vacation ;) early next week

@os97673
Copy link
Member

os97673 commented Aug 9, 2013

Ok, so it is status.nil? check which causes the problem.
But the real cause of the problem is that we call set_scenario_color on table cell value even if the table is not an examples table. In this case the table is just a data and has no status thus there is no reason to use it.

@os97673
Copy link
Member

os97673 commented Aug 9, 2013

So, for now I will just add check if cell is part of Examples table.

os97673 added a commit that referenced this issue Aug 9, 2013
…ould not used to calculate scenario's status
@os97673 os97673 closed this as completed Aug 9, 2013
tooky added a commit that referenced this issue Aug 15, 2013
…pters

* origin/master:
  Bump gherkin version
  minor history reformatting
  Release 1.3.6
  Fixed name of the tag for 1.3.5
  Fixed #493: sometimes tables is just table not part of outline and should not used to calculate scenario's status
  Remove autoformat functionality.
  Same legal issue than README.md
  Legal issue at README.md
  Release 1.3.5
  Bump multi_test.

Conflicts:
	features/docs/cli/autoformatting.feature
@lock
Copy link

lock bot commented Oct 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants