Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
IncludeTestAssembly should default to true
See original GitHub issueI just enabled coverlet on a new repository, and the coverage reports were incomplete. The root cause turned out to be a setting IncludeTestAssembly, which confusingly excluded code from the coverage report even though that code was not part of any of the various exclude properties.
Test code is an essential part of a production code base, and should always be included in coverage collection. It’s fine to provide a property so it can be disabled, but the property should default to the value users are expected to use.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Seems that exclude test project by default is the expected behavior for the majority.
I know i’m late to this party - so I’m trying to understand what people are thinking here.
A test method tests some product assembly/method. Kewl. So why do we want coverage on a test method? The tests are there to verify the product assembly is working great. The coverage is used to make sure the product assembly is tested appropriately.
I don’t see why anyone would care if a test method is … covered? All I could see that this could highlight are some ‘orphaned’ methods in the test project which are called/used any more?