Generate a code coverage report (lcov+gcov)BRL-CAD
Status: ClosedTime to complete: 72 hrs Mentors: SeanTags:

This task involves setting up and generating an lcov code coverage analysis on BRL-CAD. Wherever applicable, make sure lcov is told to ignore our src/other directory. After learning how to use the tool, discuss with the developers what portion of the code will be most useful to analyze, or scan these:

  • ''benchmark''
  • ''make test''
  • ''make regress''

Submit the results.

Uploaded Work
File name/URLFile sizeDate submitted
http://brlcad.org/brlcad-coverage/n/aDecember 03 2013 17:56 UTC
http://brlcad.org/coverage/n/aDecember 04 2013 15:02 UTC
Comments
Jacob Burroughson December 2 2013 15:50 UTCTask Claimed

I would like to work on this task.

Mandeep Kaur on December 2 2013 16:05 UTCTask Assigned

This task has been assigned to Jacob B. You have 72 hours to complete this task, good luck!

Jacob Burroughson December 3 2013 17:57 UTCReady for review

The work on this task is ready to be reviewed.

Sean on December 4 2013 02:51 UTCThis is awesome!

Jacob, this is really cool.  I've not seen an lcov report in a very very long time, long before we had unit tests.  Is it possible to hide your homedir paths in those first five?


I can see that the unit tests ran -- what else ran?  The benchmark suite (make bench)?  Just "make test"?  "make regress?"  All of them?


Would be good to see either three separate reports or (most importantly) the aggregate of all three to see how much code we hit up.


 

Sean on December 4 2013 02:51 UTCTask Needs More Work

One of the mentors has sent this task back for more work. Talk to the mentor(s) assigned to this task to satisfy the requirements needed to complete this task, submit your work again and mark the task as complete once you re-submit your work.

Sean on December 4 2013 03:06 UTCfollow-on task

A follow-on to this task has been posted: http://www.google-melange.com/gci/task/view/google/gci2013/5849379982278656


 

Jacob Burroughson December 4 2013 15:03 UTCReady for review

The work on this task is ready to be reviewed.

Sean on December 4 2013 16:28 UTCTask Closed

Congratulations, this task has been completed successfully.