You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Initial run: Run test coverage and record which testmethodes/testclass/testfile "covered" a production code line/method/class
Get changed files/functions/classes for a commit
Lookup the testmethods/testclass/testfile that cover the files/functions/classes for the commit
Execute the found testmethods/testclass/testfile
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.
The text was updated successfully, but these errors were encountered:
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?
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.
The text was updated successfully, but these errors were encountered: