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
The junit.jupiter.conditions.deactivate configuration parameter is used to deactivate ExecutionConditions such as the the DisabledCondition that is built into JUnit Jupiter (org.junit.jupiter.engine.extension.DisabledCondition).
That configuration parameter is not used to filter out test classes or test methods.
When you set it to * or org.*, those patterns match org.junit.jupiter.engine.extension.DisabledCondition and therefore deactivate @Disabled, which allows both of the test methods in your class to run.
Thus, the behavior you have described is to be expected.
In order to filter tests within your Gradle build, you will need to use the Test Filtering support provided by Gradle.
When using
junit.jupiter.conditions.deactivate
, it is not behaving as expected.Pattern Matching Syntax
The path to the test file is as follows
(This test file has one normal test and one disabled test.)
Depending on the value of
junit.jupiter.conditions.deactivate
, I got the following results.*
org.*
org.example.*
org.example.DisableTest
Am I misunderstanding the usage?
If it is a bug, can I try to fix it?
I think the
ClassNamePatternFilterUtils
needs fixing.Steps to reproduce
https://github.com/dev-jonghoonpark/junit5-example-class-name-pattern-filter-utils
I've created a systemProperty in gradle for each case.
You can uncomment each case to test it.
Context
Deliverables
The text was updated successfully, but these errors were encountered: