Allow control of merged coverage results behaviour
@jakubch1 is already working on this.
Since Nov 1, 2022.
Assessment
This issue has not been assessed yet.
Description
@MarcoRossignoli
For the moment, we don’t offer a way to disable the merging. Can you open an issue on https://github.com/microsoft/vstest/issues so we can collect the community interest on this feature and prioritize it? Can you also explain, if possible, what’s your scenario and the reason not to have a merged global report?
Steps to reproduce
Create two test projects each with runsettings specifying different results directories and run tests at the same time.
Expected behavior
Separate results
Actual behavior
There is only a single merged results.
Scenario
Currently I am a contributor to a code coverage vs extension that is triggered by the test explorer and will create individual cobertura files for each project ( by running OpenCover or Coverlet for each test project ) that can be viewed by the developer if required. These cobertura files are then used to create a single merged html report.
The extension will shortly permit using Ms code coverage over the existing tools.
So ultimately a merged report is what I require but for consistency I would like the individual results given that vstest has access to them.
- Dominant language
- C#
- Stars
- 125
- Forks
- 17
- Avg merge
- 1h 17m
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/codecoverage
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
microsoft/codecoverage#246 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
microsoft/codecoverage#237 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/codecoverage#234 · 1 comment · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
microsoft/codecoverage#233 · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
microsoft/codecoverage#232 · 6 comments ·
All issues in microsoft/codecoverage
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·