Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Better debug output #240

Open
acoburn opened this issue Oct 11, 2018 · 0 comments
Open

Better debug output #240

acoburn opened this issue Oct 11, 2018 · 0 comments

Comments

@acoburn
Copy link

acoburn commented Oct 11, 2018

The test suite generates a nice HTML report summary, but there is little indication of why a particular test fails. Adding debug output is no help if the test case encounters an exception (e.g. if it can't parse a link header as described in #232). There is an output log file, but that isn't particularly helpful in most cases (no stack traces are output). The RDF-based output file has some better diagnostic information, but the format is incredibly hard to read. Some sort of debug output switch would be much more helpful. And if there already exists such a thing, please document it in the README.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant