Closed MisinformedDNA closed 1 year ago
I would suggest that you go with option 4. Your scenario seem to be really rare.
Regarding the other options:
- Copy
summary.html
toindex.html
.
This could cause problem if you generate other formats as well.
- Add a parameter to name the summary file.
Definitely "no". I try to keep the number of parameters as low as possible. Nobody likes to read the documentation for 100 parameters.
- Add a new report
HtmlSummary_AzurePipelines
.
The behavior would then be different from the other summary reports.
I have a very similar case where, due to the number of classes, generating the report takes a 3-5 minutes. However, generating the HtmlSummary takes only a few seconds.
Option 4 does not work when I simultaneously use publishCodeCoverageResults: true.
Option 2 or 3 would be very useful.
@marcinsku I will have a look within the next days.
@marcinsku
HtmlSummary and _Html_BlueRedSummary report types now also create an index.html file.
This file will be displayed in Azure DevOps if you use the publishCodeCoverageResults: true
option.
I will publish a new release within the next days.
That's great! Thank you for the quick response.
New release 5.3.7 is now available.
Describe the bug Because of the size of our repo, when code coverage files are generated with
HtmlInline_AzurePipelines
, we run out of space on our hosted agent.HtmlSummary seemed like a good solution, but it generates a summary.html file, which is not picked up by the Azure Pipeline UI:
Some options:
summary.html
toindex.html
.HtmlSummary_AzurePipelines
.