-
Notifications
You must be signed in to change notification settings - Fork 53
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
Gradle 'check' task runs tests from all project, despite no verification rules are added. #168
Comments
Hi, This behavior can be changed only if you configure the Kover accordingly: it is enough to set the value for the flag
To better understand your issue, could you clarify the version of the plugin, the structure of the project and which command you run the checks with. |
I have created a sample project: The Kover documentation contains the following: By default, for the task koverVerify coverage is calculated only for the tests of the one project. If classes or functions are called from tests of another module, then you need to set a flag runAllTestsForProjectTask for KoverExtension to true (see). In this case, The project configured with:
The expected behavior would be:
|
In a gradle multi project running a subproject 'check' task trigger all tests from all projects.
No verification rules are added to 'koverVerify' task.
The documentation said:
"if verification rules are added, then running tasks koverVerify or check will trigger the execution of all active tests from all projects!"
If no verification rules are added, then the 'koverVerify' task will be disabled (skipped), but it depends on all tests and 'check' task depends on 'koverVerify', so despite the 'koverVerify' is skipped it forces gradle to run all tests from all projects.
The text was updated successfully, but these errors were encountered: