[petsc-dev] tests coverage

[Jed Brown]

We should report coverage to GitLab, in which case it'll annotate the diff. For example, this MR shows a red mark on this line that isn't covered by the tests, versus green marks for the covered changes.

https://gitlab.com/micromorph/ratel/-/merge_requests/199/diffs#9f067f1470c81c8dda08481fdd5c6deeba9a035a_341_346

Satish Balay via petsc-dev <petsc-dev at mcs.anl.gov> writes:

> There is some coverage info - there are a couple of gcov tests - but
> that doesn't show coverage from all tests.
>
> For ex: https://gitlab.com/petsc/petsc/-/merge_requests/5509
>
> click on the last stage/job of the pipeline 'analyze-pipeline' i.e
> https://gitlab.com/petsc/petsc/-/jobs/2841119765
>
> Here - browse 'artifacts' i.e
> https://gitlab.com/petsc/petsc/-/jobs/2841119765/artifacts/browse
>
> Here go to 'arch-ci-analyze-pipeline' and click 'index_gcov.html' i.e:
> https://petsc.gitlab.io/-/petsc/-/jobs/2841119765/artifacts/arch-ci-analyze-pipeline/index_gcov.html
>
> Satish
>
> On Fri, 12 Aug 2022, Blaise Bourdin wrote:
>
>> Hi,
>> 
>> Is the source coverage analysis by the tests easily available? When submitting a MR, I want to know if adding a test is necessary.
>> 
>> Regards,
>> Blaise
>> 
>> 
>> — 
>> Tier 1 Canada Research Chair in Mathematical and Computational Aspects of Solid Mechanics
>> Professor, Department of Mathematics & Statistics
>> Hamilton Hall room 409A, McMaster University
>> 1280 Main Street West, Hamilton, Ontario L8S 4K1, Canada 
>> https://www.math.mcmaster.ca/bourdin | +1 (905) 525 9140 ext. 27243
>> 
>>