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

With lots of tests, SKIPPING in console is tediously verbose. #1111

Closed
johnjbarton opened this issue Jun 25, 2014 · 2 comments · Fixed by #1115 · May be fixed by Omrisnyk/npm-lockfiles#122 or Omrisnyk/npm-lockfiles#132
Closed

With lots of tests, SKIPPING in console is tediously verbose. #1111

johnjbarton opened this issue Jun 25, 2014 · 2 comments · Fixed by #1115 · May be fixed by Omrisnyk/npm-lockfiles#122 or Omrisnyk/npm-lockfiles#132

Comments

@johnjbarton
Copy link
Contributor

...and I have a small PR to make it betta.

@caitp
Copy link

caitp commented Jun 25, 2014

it is, but you can use filters to ignore them (workaround)

johnjbarton added a commit to johnjbarton/karma that referenced this issue Jun 26, 2014
Before: hundreds of SKIPPING lines in console.log.
After: A single summary line with a count.

Closes karma-runner#1111
@johnjbarton
Copy link
Contributor Author

Unfortunately the filters omit the success responses.

johnjbarton added a commit to johnjbarton/karma that referenced this issue Jun 30, 2014
Before: hundreds of SKIPPING lines in console.log.
After: A single summary line with a count.

Closes karma-runner#1111
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants