Skip to content
This repository was archived by the owner on Jan 10, 2024. It is now read-only.

fix failed count in ConsoleReporter when there are skipped_or_pending_specs #150

Merged
merged 1 commit into from
Dec 11, 2014
Merged

fix failed count in ConsoleReporter when there are skipped_or_pending_specs #150

merged 1 commit into from
Dec 11, 2014

Conversation

larsklevan
Copy link
Contributor

The failures output in ConsoleReporter is incorrect if skipped_or_pending_specs is greater than 0.

Running:

rake spec:javascripts SPEC=myspec

Before:

4 specs, 2081 skipped or pending, -2081 failures in 0.43s.

After:

4 specs, 2081 skipped or pending, 0 failures in 0.43s.

Verified that it works if you run the whole test suite and if there is a failure.

searls added a commit that referenced this pull request Dec 11, 2014
…-with-filter

fix failed count in ConsoleReporter when there are skipped_or_pending_specs
@searls searls merged commit 059c123 into testdouble:master Dec 11, 2014
@searls
Copy link
Member

searls commented Dec 11, 2014

Thanks!

@searls
Copy link
Member

searls commented Dec 11, 2014

Landed in 0.10.4

@dgrawunder
Copy link

This fix causes wrong failed count if skipped or pending specs are present. Reverting this fix solves the problem. Even with the reverted fix I am not able to reproduce the problem leading to this fix.

@searls
Copy link
Member

searls commented Dec 18, 2014

@larsklevan can you please try to work with @dgrawunder to understand what went wrong?

@larsklevan
Copy link
Contributor Author

I tested this again with a clean sandbox and it looks like my patch is incorrect. I must have overridden something in my environment that was causing it to break. My apologies for not testing it better - please revert the patch.

searls added a commit that referenced this pull request Dec 18, 2014
revert PR #150 - was causing incorrect failed count when pending or skipped specs are present
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