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.

Sign up for GitHub

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

Jump to bottom

Print one failure per suite with forbid-only/forbid-pending #3031

Closed
ScottFreeCode opened this issue Sep 29, 2017 · 1 comment
Closed

Print one failure per suite with forbid-only/forbid-pending #3031

ScottFreeCode opened this issue Sep 29, 2017 · 1 comment
Labels
semver-major implementation requires increase of "major" version number; "breaking changes" stale this has been inactive for a while...

Comments

@ScottFreeCode
Copy link
Contributor

As of #2874, forbid-only and forbid-pending print one failure for each test in a suite that is marked only or skip. It would be neater if they just printed one failure per suite. This would probably also solve #2944, which is a more critical correctness issue where this is... just a matter of good output.
@ScottFreeCode ScottFreeCode added the semver-major implementation requires increase of "major" version number; "breaking changes" label Sep 29, 2017
@github-actions
Copy link
Contributor

This issue hasn't had any recent activity, and I'm labeling it stale. Remove the label or comment or this issue will be closed in 14 days. Thanks for contributing to Mocha!

@github-actions github-actions bot added the stale this has been inactive for a while... label Mar 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
semver-major implementation requires increase of "major" version number; "breaking changes" stale this has been inactive for a while...
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ScottFreeCode