Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Record test method that covered function/class for test impact analysis #1566

Open
SystemCheater opened this issue Dec 6, 2023 · 2 comments
Labels
question This issue is a question stale waiting for customer Waiting for customer action

Comments

@SystemCheater
Copy link

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.

@github-actions github-actions bot added the untriaged To be investigated label Dec 6, 2023
@Bertk Bertk added feature-request New feature request waiting for customer Waiting for customer action and removed untriaged To be investigated labels Dec 10, 2023
@Bertk
Copy link
Collaborator

Bertk commented Dec 10, 2023

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?

@Bertk Bertk added question This issue is a question and removed feature-request New feature request labels Feb 11, 2024
Copy link

This issue is stale because it has been open for 3 months with no activity.

@github-actions github-actions bot added the stale label May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question This issue is a question stale waiting for customer Waiting for customer action
Projects
None yet
Development

No branches or pull requests

2 participants