-
Notifications
You must be signed in to change notification settings - Fork 0
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
Conversation
end | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
noise
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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?)
There was a problem hiding this comment.
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.
Committed |
Looks good. I recommend splitting the should-to-expect changes into their own commit. If necessary, the gemspec can depend on RSpec This would leave example-to-notification as a second commit and make it more obvious that the tests didn't change. |
Comments addressed. I will need to fix up the tap formatter before all tests pass as well. |
Looks great. |
The spec for |
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. |
JUnitFormatter works with RSpec 3
No description provided.