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

Various default behavior in report phase between html, xml, and command line report #231

Closed
nedbat opened this issue Jan 10, 2013 · 2 comments
Labels
bug Something isn't working html

Comments

@nedbat
Copy link
Owner

nedbat commented Jan 10, 2013

Originally reported by Danny Handoko (Bitbucket: dhandoko, GitHub: dhandoko)


The default behavior of coverage report, coverage html, and coverage xml differs in regards to error handling. If source file is not found, coverage report goes ahead with reporting next sources, coverage html aborts the report creation, resulting in incomplete html directory. Similar behavior with coverage report is achieved when option -i is used.

Also coverage html reports that the source cannot be found, but does not inform the user that the report generation is aborted. Visible message about this, and advise to use -i is an alternative to help the user out of this confusing situation.

See attachments for a testcase to reproduce the situation


@nedbat
Copy link
Owner Author

nedbat commented Jun 2, 2016

Original comment by alsopape (Bitbucket: alsopape, GitHub: Unknown)


suggested a documentation fix to this here over on the github mirror

@nedbat
Copy link
Owner Author

nedbat commented Jun 2, 2016

Fixed in be88cf4 (bb)

@nedbat nedbat closed this as completed Jun 2, 2016
@nedbat nedbat added minor bug Something isn't working html labels Jun 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working html
Projects
None yet
Development

No branches or pull requests

1 participant