Re: [GRASS-dev] [GRASS GIS] #3819: Add test coverage of C files

[GRASS GIS]

#3819: Add test coverage of C files
--+-
  Reporter:  pmav99   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:
 Component:  Compiling|Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by rouault):

 > GDAL is already using gcov/lcov, too, so it might make sense to see how
 they have integrated them

 This is quite messy to be honest. Partly because I didn't try to make this
 better :-) So basically, I've a job that forks the GDAL master branch and
 re-applies the following changes on top of it :
 
https://github.com/rouault/gdal_coverage/commit/3b63c70890a0897dcbe1cbd49f36b76e0a5e704a
 But the gist is build with lcov, run the tests, run lcov, filter some
 stuff in its output to have a clean report, run genhtml and then push this
 to a github repo. The interesting part that could be more or less reused
 by GRASS is in
 
https://github.com/rouault/gdal_coverage/commit/3b63c70890a0897dcbe1cbd49f36b76e0a5e704a
 #diff-46c965c7db8bedae7518f42e783c44dd

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3819: Add test coverage of C files

[GRASS GIS]

#3819: Add test coverage of C files
--+-
  Reporter:  pmav99   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:
 Component:  Compiling|Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by pmav99):

 For the record, GDAL is already using gcov/lcov, too, so it might make
 sense to see how they have integrated them: https://gdalautotest-coverage-
 results.github.io/coverage_html/index.html

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev