Coverage report tweaks

[nikoyak]

Proposed Changes

This PR:

• Restores the GenerateCoverageReport dependency chain broken in Closes #262, closes #270 #271
• Сloses Coverage information is blocked by itself #251
• Adds the handy ShowCoverageReport target to the library template

Types of changes

What types of changes does your code introduce to MiniScaffold?

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• Build and tests pass locally
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)

Further comments

Unclosed question on test coverage verification. It is not necessary to evaluate test coverage every time you run tests, and to speed up feedback, it is inconvenient to write the cmd /c "set DISABLE_COVERAGE=1& build DotnetTest" command on Windows, for example. I propose to change the logic and replacing the environment variable with ENABLE_COVERAGE. And local testing with test coverage is convenient to do with a new ShowCoverageReport target. What do you think?

[TheAngryByrd]

Unclosed question on test coverage verification. It is not necessary to evaluate test coverage every time you run tests, and to speed up feedback, it is inconvenient to write the cmd /c "set DISABLE_COVERAGE=1& build DotnetTest" command on Windows, for example. I propose to change the logic and replacing the environment variable with ENABLE_COVERAGE. And local testing with test coverage is convenient to do with a new ShowCoverageReport target. What do you think?

This is kind of tough call, some people use the coverage in their IDE to see things being covered, but coverage does slow down tests considerably. I'm leaning toward your suggestion though but I wouldn't be surprised if I get another issue down the road as to default have coverage on.

[TheAngryByrd]

Want me to merge this or wait for the ENABLE_COVERAGE change?

[nikoyak]

Want me to merge this or wait for the ENABLE_COVERAGE change?
Wait