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

Let the JUnitFormatter mark skipped tests as failures in strict mode #543

Merged
merged 1 commit into from
Jun 13, 2013

Conversation

brasmusson
Copy link
Contributor

Let the option strict make the JUnitFormatter to mark skipped tests as failures.

Use a new interface StrictAware to determine which formatters the strict option should be passed to, following the example of the interface ColorAware determining which formatters the monochrome option is sent to.

Let the option strict make JUnitFormatter to mark skipped tests as
failures. Use a new interface StrictAware to determine which formatters
the strict option should be passed to, following the example of the
interface ColorAware determining which formatters the monochrome option
is sent to.
@aslakhellesoy
Copy link
Contributor

That was quick! I had to restart the travis build, but it looks good to me.

@lucas1000001 can you merge this one in?

Aslak

@ghost ghost assigned notmattlucas Jun 13, 2013
@notmattlucas
Copy link
Contributor

Sure will do.

notmattlucas added a commit that referenced this pull request Jun 13, 2013
Let the JUnitFormatter mark skipped tests as failures in strict mode
@notmattlucas notmattlucas merged commit 9a6fe57 into cucumber:master Jun 13, 2013
@notmattlucas
Copy link
Contributor

Built and tested fine locally - merged in.

@aslakhellesoy
Copy link
Contributor

@lucas1000001 thanks - don't forget to update History.md

notmattlucas added a commit that referenced this pull request Jun 13, 2013
@notmattlucas
Copy link
Contributor

Oops, sorry, done :)

@brasmusson brasmusson deleted the junit-formatter-strict branch June 28, 2013 11:01
@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 unassigned notmattlucas Oct 25, 2018
@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

Successfully merging this pull request may close these issues.

3 participants