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

JUnitFormatter works with RSpec 3 #1

Merged
merged 5 commits into from
Mar 26, 2014
Merged

JUnitFormatter works with RSpec 3 #1

merged 5 commits into from
Mar 26, 2014

Conversation

mrerrormessage
Copy link

No description provided.

end

Copy link

Choose a reason for hiding this comment

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

noise

Copy link
Author

Choose a reason for hiding this comment

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

you think I should leave it?

Copy link

Choose a reason for hiding this comment

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

In some places you changed the whitespace around examples and groups, in others you did not. Either way, I suppose.

(I'm assuming we're going to open a PR upstream?)

Copy link
Author

Choose a reason for hiding this comment

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

Fair enough, I'll make it consistent.

@cbandy
Copy link

cbandy commented Mar 25, 2014

Committed lib/rspec-extra-formatters/.junit_formatter.rb.swp and spec/rspec-extra-formatters/.junit_formatter_spec.rb.swp.

@cbandy
Copy link

cbandy commented Mar 25, 2014

Looks good. I recommend splitting the should-to-expect changes into their own commit. If necessary, the gemspec can depend on RSpec >= 2.11.0.

This would leave example-to-notification as a second commit and make it more obvious that the tests didn't change.

@mrerrormessage
Copy link
Author

Comments addressed. I will need to fix up the tap formatter before all tests pass as well.

@cbandy
Copy link

cbandy commented Mar 26, 2014

Looks great.

@cbandy
Copy link

cbandy commented Mar 26, 2014

The spec for TapFormatter.start is a little awkward, but incorporating it into the existing test seems best for now.

@mrerrormessage
Copy link
Author

I agree it is an awkward spec, that was my thought. Dump summary is completely not needed now that rspec is using the observer pattern.

mrerrormessage added a commit that referenced this pull request Mar 26, 2014
JUnitFormatter works with RSpec 3
@mrerrormessage mrerrormessage merged commit 235ab93 into master Mar 26, 2014
@mrerrormessage mrerrormessage deleted the rspec-3 branch March 26, 2014 20:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants