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

Add automatic instrumentation filter to project classes #418

Open
shanshin opened this issue Jun 27, 2023 · 0 comments
Open

Add automatic instrumentation filter to project classes #418

shanshin opened this issue Jun 27, 2023 · 0 comments
Assignees
Labels
Feature Feature request issue type S: postponed Status: work on the issue is not in the short term plans

Comments

@shanshin
Copy link
Collaborator

Due to the incompatibility of some libraries with Kover instrumentation, errors may occur in the instrumentation of classes that are not related to the project.
There is a need to filter out all classes that are not related to projects.

This can be implemented by performing the tasks of compiling all dependencies strictly before running the tests, finding packages that relate to the application, and transferring these packages to the CommandLineArgumentProvider.

This solution has the following disadvantages:

  • Kover implicitly add dependencies to the build between compilation Gradle tasks and test tasks
  • If the compilation task depends on the testing task of another project, and project is specified as a Kover dependency, then a cyclic dependency between tasks appears
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Feature request issue type S: postponed Status: work on the issue is not in the short term plans
Projects
None yet
Development

No branches or pull requests

1 participant