On reflection I think it's OK as it is. You might want to generate coverage for a subset of the tests while doing some test development or trying to reduce the number of tests while maintaining coverage - so it would be useful to be able to just generate a report after running the tests you care about.
On Mon, Oct 23, 2017 at 3:27 PM, Jiri Daněk (JIRA) <[email protected]> wrote: > > [ https://issues.apache.org/jira/browse/PROTON-1622?page= > com.atlassian.jira.plugin.system.issuetabpanels:comment- > tabpanel&focusedCommentId=16215211#comment-16215211 ] > > Jiri Daněk commented on PROTON-1622: > ------------------------------------ > > I'll fix the other things except the make target. I haven't figured how to > run the tests from the target. > > > Add coverage reporting to CMake build > > ------------------------------------- > > > > Key: PROTON-1622 > > URL: https://issues.apache.org/jira/browse/PROTON-1622 > > Project: Qpid Proton > > Issue Type: Improvement > > Components: proton-c > > Affects Versions: proton-c-0.18.0 > > Reporter: Jiri Daněk > > Assignee: Justin Ross > > Priority: Minor > > Labels: patch, testing > > Fix For: proton-c-0.19.0 > > > > > > This improvement is intended to cover > > * Reporting coverage from Python code > > * Upload of Python and C/C++ coverage data from Travis CI to codecov.io > for easy viewing > > > > -- > This message was sent by Atlassian JIRA > (v6.4.14#64029) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
