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

fix issue #124 - JUnit expand option #808

Merged
merged 2 commits into from
Mar 14, 2015

Conversation

richarda
Copy link
Contributor

@mattwynne Started looking at #124. For now, this failing unit test highlights the problem. I'm still looking at formatter/junit.rb to see if that's the place to handle @option[:expand]

@richarda richarda changed the title add failing tests for issue #124 fix ssue #124 - JUnit expand option Feb 14, 2015
@richarda richarda changed the title fix ssue #124 - JUnit expand option fix issue #124 - JUnit expand option Feb 14, 2015
end

context "In --expand mode" do
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is where the new tests start. Everything above was just moved into a context.

@written_files[feature_filename] = data
module Cucumber
module Formatter
describe Junit do
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changed module Cucumber::Formatter to

module Cucumber
  module Formatter

to get runtime

@mattwynne
Copy link
Member

I'm starting to feel guilty about pinging you about this one @richarda - it might well be too horrible to be worth it.

For version 3.0, I want to re-write the formatters to use the new, much simpler formatter API, precisely to get rid of bugs like this. So if it looks too tricky, we can just put it into the 3.0 milestone and expect it to get fixed then.

@richarda
Copy link
Contributor Author

Don't feel guilty @mattwynne ...
I have noticed the reports in our Jenkins builds have Scenario Outlines with missing details. I'm glad to now know why 😄

A silver lining:
I do think our team has a tendency to overuse the scenario outline anyway, so if this waits until 3.0, it will be a another good reason to take a hard look at improving our features. I'm sure there are good uses of the outline, but I often see a lot of incidental details in outlines, (redundant examples that don't help clarify behavior), which makes we wonder if the outline is a bit of a crutch for some people (including me).

@mattwynne mattwynne modified the milestone: 2.0 Mar 10, 2015
@mattwynne mattwynne added the 🐛 bug Defect / Bug label Mar 13, 2015
@mattwynne mattwynne modified the milestones: 2.0, 2.1 Mar 13, 2015
@brasmusson brasmusson merged commit 06264ea into cucumber:master Mar 14, 2015
@brasmusson
Copy link
Contributor

The actual fix of the issue is in cucumber/common@75b0975.

@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
🐛 bug Defect / Bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants