Skip to content

Combine/Merge/Union/Collect results and print without running tests #822

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
PeterOeClausen opened this issue Apr 21, 2020 · 2 comments
Closed
Labels
question This issue is a question

Comments

@PeterOeClausen
Copy link

We have just begun using Coverlet for code coverage in the project I'm working on.

We have two NET CORE projects for testing, one "quick" for unit testing, and one "slow" for functional tests that queries a real database.

These two test projects run in parallel in a GitLab environment through GitLab pipeline jobs (which is like GitHub actions).

As these run in parallel, I do not believe MergeWith is an option, because it requires us to run one test project, then the next, combining with the first.

We want to collect Coverlet coverage reports and combine/merge/union/collect (many words for the same thing) the results and print them in a final pipeline job.

Question: Is there a way to run Coverlet in a way, to give it reports as arguments, to combine these, and then print the result?

I know that tools like ReportGeneration and Coveralls.io exists for combining reports and visualizing them for analysis. But what we want for now is just to print the result as if we were running tests, without having to re-run our tests. Is that currently possible?

@MarcoRossignoli MarcoRossignoli added the question This issue is a question label Apr 21, 2020
@MarcoRossignoli
Copy link
Collaborator

Question: Is there a way to run Coverlet in a way, to give it reports as arguments, to combine these, and then print the result?

No this is not supported at the moment, we're discussing about adding these features to coverlet dotnet tool driver #704

There is also some plan of vstest team that in future could help with this(only if you run collectors version and run in parallel in the same "test session") microsoft/vstest#1811.

@MarcoRossignoli
Copy link
Collaborator

Close for solved issue, feel free to re-open if needed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question This issue is a question
Projects
None yet
Development

No branches or pull requests

2 participants