Improve Coverage Report by displaying what is not documented #61

Closed
Rukenshia opened this Issue Aug 30, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@Rukenshia

I am currently documenting a lot of code. Currently, my work flow is like "do what you see is missing in your files and then run esdoc to see how much is covered". esdoc always provides me a neat percentage for each file, but maybe this could be taken even further to display what is not covered yet. Im currently stuck in a few files with like 70/71 and whatever and it is pretty hard to find what's missing right now.
Maybe it is possible to mark the lines in the source page for each file of esdoc? I would pretty much love that. If you can already measure how much is covered, I guess it should be possible to check what is not covered.

@h13i32maru

This comment has been minimized.

Show comment
Hide comment
@h13i32maru

h13i32maru Aug 30, 2015

Member

I understood your request. And I think that it is pretty good!
I consider UI of coverage detail. Please wait a some time because the UI is difficult.
Thanks.

Member

h13i32maru commented Aug 30, 2015

I understood your request. And I think that it is pretty good!
I consider UI of coverage detail. Please wait a some time because the UI is difficult.
Thanks.

@h13i32maru

This comment has been minimized.

Show comment
Hide comment
@h13i32maru

h13i32maru Sep 6, 2015

Member

Now, I published ESDoc v0.2.5.
With this version, you can see undocumentation lines.

  1. click Source in header
  2. click your not 100% coverage file link

2015-09-06 19 14 31

Member

h13i32maru commented Sep 6, 2015

Now, I published ESDoc v0.2.5.
With this version, you can see undocumentation lines.

  1. click Source in header
  2. click your not 100% coverage file link

2015-09-06 19 14 31

@h13i32maru h13i32maru closed this Sep 6, 2015

@Rukenshia

This comment has been minimized.

Show comment
Hide comment
@Rukenshia

Rukenshia Sep 6, 2015

Awesome, thank you!

Awesome, thank you!

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