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

Find a way to make reporting less verbose #8

Closed
contolini opened this issue May 29, 2015 · 2 comments
Closed

Find a way to make reporting less verbose #8

contolini opened this issue May 29, 2015 · 2 comments

Comments

@contolini
Copy link
Member

Some sites report hundreds of potential problems which can be overwhelming to scroll through. The problems often have the same message but occur on different lines.

Maybe we should cap the list by default. Something like:

  ⚠  499 potential problems found.

  ⚠  183:70 Anchor text may not identify the link destination.
  ⚠  183:174 Anchor text may not identify the link destination.
  ⚠  183:243 Anchor text may not identify the link destination.
  ⚠  183:295 Anchor text may not identify the link destination.
  ⚠  183:351 Anchor text may not identify the link destination.
  ⚠  183:409 Anchor text may not identify the link destination.
  ⚠  183:467 Anchor text may not identify the link destination.
  ⚠  183:522 Anchor text may not identify the link destination.
  ⚠  183:579 Anchor text may not identify the link destination.
  ⚠  183:638 Anchor text may not identify the link destination.
  ⚠  183:694 Anchor text may not identify the link destination.
  ⚠  183:749 Anchor text may not identify the link destination.

  487 additional problems not shown. Run with `--verbose` to show full list.

Or maybe we should just group similar errors?

  ⚠ 183:70, 183:174, 183:243, 183:295, 183:351, 183:409, 183:467, 183:522, 183:579, 183:638, 183:694, 183:749 Anchor text may not identify the link destination.

Or:

  ⚠ Anchor text may not identify the link destination. Occurs at 183:70, 183:174, 183:243, 183:295, 183:351, 183:409, 183:467, 183:522, 183:579, 183:638, 183:694, 183:749.

Example of the problem:

screen shot 2015-05-29 at 2 17 13 pm

@wpears
Copy link
Member

wpears commented May 29, 2015

I like the third option, you'd get complete information without taking up unnecessary screen space.

@zrrrzzt
Copy link
Contributor

zrrrzzt commented May 29, 2015

I like the third option as well.
If we are going to implement more control of the output it would be nice to have an option for just the errors and one for only PASS/FAIL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants