coverage #237

Activity

1. den-run-ai

   added

   enhancement

   decision

   on Sep 4, 2016
2. vmuriart commented on Feb 1, 2017

   

   vmuriart

   on Feb 1, 2017

   Contributor

   More actions

   Semi-closed. Still needs coverage from Travis, waiting on SharpCover or MonoCover. Alternatively, OpenCover may work under Core .net
3. vmuriart

   added

   Mono (Linux and OSX)

   and removed

   decision

   on Feb 1, 2017
4. den-run-ai

   added this to the 2.3.0 milestone on Feb 2, 2017
5. vmuriart commented on Feb 22, 2017

   

   vmuriart

   on Feb 22, 2017

   Contributor

   More actions

   Coverage was added to .net through AppVeyor when running embedded and python tests. There is no mature & maintained coverage for mono. For some of the existing tools, they don't conform any existing coverage file format. It's even looking bleak in core dotnet since OpenCover isn't currently actively working on it.

   I think the milestone should be removed on this one or closed as fixed. Thoughts? @denfromufa
6. den-run-ai

   removed this from the 2.3.0 milestone on Feb 22, 2017
7. den-run-ai commented on Feb 22, 2017

   

   den-run-ai

   on Feb 22, 2017

   ContributorAuthor

   More actions

   @vmuriart agreed, it least some coverage!
8. den-run-ai

   closed this as completedon Feb 22, 2017
9. vmuriart

   added this to the 2.3.0 milestone on Feb 22, 2017
10. vmuriart commented on Feb 22, 2017

    

    vmuriart

    on Feb 22, 2017

    Last edited by vmuriart

    Contributor

    More actions

    Readded the milestone so that it counts towards v2.3.0. 🤓 I had meant to either remove milestone or close issue.

    https://emptysqua.re/blog/code-coverage-python-c-extensions/