the-dext / runcoverletreport Goto Github PK

Add ability to detect coverlet.MSBuild, coverlet.collector or display an error if neither package is found.

Disabling MSBuild in the settings did the trick. Now it's working.
Is it possible to add some auto detection?
And maybe output a warning if neither collector or MSBuild package is referenced.

Originally posted by @danielpalme in #1 (comment)

After runnig the tool the following error will be displayed:

Could not find file TempPath-GUID-\coverage.cubertura.xml

The given location exist, but contains an empty folder name "coverageReport".

Hi,

First of all, this is a great VS extension!

But when I try to cover one of my project, I don't expect the whole solution got restored/built/tested.

Is there any options/settings to let me just run the coverage against the select test project?

Sometimes the first window has an error at the end and It closes before I can try to pause or read it. Having those go to the output window would make it easier to understand what is happening. Would @the-dext consider a PR that just ran the tools and redirected stdout to the output window (and possibly the error list)?

The title of the dialog box is the default "Microsoft Visual Studio" and the message is the quoted value from the issue title.

Are there any options I can set to capture the console output or whatever else may be contributing to create this error?

When a solution contains a Docker Compose Project (*.dcproj) the plugin fails to execute the tests.

Would it be possible to add an open-source license to this repository?
I really like the extension and the help it provides, but unfortunately, it seems as if the work on the projects has stopped.
Without a license, I would not be able to make any modifications to the project for my use case.
Thank you in advance.

I keep forgetting to save the code before running this and then have to just re-run it again. Is there an option to do this or call build for the project (which should save the files)?

I updated my Visual Studio 2022 to the latest version 17.7.6 but now Run Coverlet Report throws an error. Can the extension be updated to work with the new VS version?

I'm using VS2019 16.8.4. If i run a new coverage report and toggle the "Tools -> Toggle Code Coverage Highlighting" the coverage is shown in the VS texteditor. But when i scroll down and back up the highlighting disappears.

Do you have any idea what might be wrong? Please let me know if i can help somehow.

Our build process has a number of additional parameters we pass to Coverlet when we run - things like ExcludeByAttribute, SkipAutoProps, etc. It would be great if there was a way to pass those in as well, so our local runs are closer to the build process.

Steps to reproduce:
Exclude one assembly/pattern from the code coverage (in tools > run coverlet report parameters)
Run in collector mode
=> The assembly in not excluded from the coverage report

Root cause: ExcludeAssemblyPatterns is used to hydrate a local variable that is not used in the command args.

Hi!

ReportGenerator now has a PRO version.

However, currently, there is nowhere where license code may be added. There is a new -license argument as can be seen here.

My suggestion is to add a new item in options so that we may add license code.

Regards,

As in title.