Skip to content

make a variant that can accept the coverage data to be provided from elsewhere #9

Description

@marc-portier

Is your feature request related to a problem? Please describe.

We currently had to drop the usage of pycoverage because it cannot accept the coverage data to be produced by another means.
(in our case an external makefile that needs bash and docker to create the environment in which the tests should run)

Describe the solution you'd like

For our specific case it would be grand if we can disable the actual testing being done here, just handle that in a previous step in the flow (i.e. our makefile) and then just feed the results from that previous step to this one, and then still benefit from all the good PR integration stuff.

Describe alternatives you've considered

None.
Well, maybe this: general separation of concerns: make multiple smaller things that can collaborate rather then one that does it all?

Additional context

Yes, as described in vliz-be-opsci/py-RDF-store#31
Note. This somewhat relates to the general feeling expressed in #8 as well: a call to maybe/optionally do less 🤔

Also: willing to lend a hand, but haven't even started looking at any of this... (so could use some tips / suggestions / feedback)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions