Open SystemCheater opened 6 months ago
Hi, thank you for the feature request but this is not the core scope of a code coverage tool.
The motivation is that our products are quiet huge and I want to reduce the feedback time in our CI/CD cycle. (And Microsoft's solution seems not to work properly with current vstest versions and current use cases.)
Can you please add some information why Microsofts TIA solution is not appropriate for your project?
This issue is stale because it has been open for 3 months with no activity.
I am looking for a possibility to introduce a test impact analysis (similar to Microsoft's initial efforts around 2017) to our C# products. The motivation is that our products are quiet huge and I want to reduce the feedback time in our CI/CD cycle. (And Microsoft's solution seems not to work properly with current vstest versions and current use cases.)
The test impact analysis should work as followed:
To enable this process coverlet should support a possibility to record the covering test unit (e. g. test method, test class or test file). To avoid accumulating large amounts of data it would be enough to record the covering test unit not on a line base (as coverage currently does) but on a method/property, class or even file level.