We discussed this in the team and think we could add a --exclude-methodname option to the ConsoleLauncher that would be implemented as a PostDiscoveryFilter and match the specified regex against the fully-qualified method name without parameters.

For example, --exclude-methodname=.+#methodName would exclude all methods called methodName from all classes.

Thanks @marcphilipp, any rough timeline for this feature?

@kishoretak, we have not scheduled this feature for any upcoming milestone.

As you can see from the assigned labels, we put this in the status: waiting-for-interest category.

However, I just added the up-for-grabs label to indicate that we would accept a contribution from the community.

May I give it a try? Do I need to deliver the following items like issue 313?

• Introduce include and exclude filter support for methods in a new MethodFilter class (similar to ClassFilter).
• Introduce include and exclude filter support for methods in the Gradle JUnit Platform plugin.
• Introduce include and exclude filter support for methods in the JUnitPlatform runner (e.g., @IncludeMethods and @ExcludeMethods).

@Sakieye,

Thanks for volunteering. Since it's up-for-grabs, anyone is welcome to submit a PR.

Please note, however, that issue #313 is very old. The Gradle JUnit Platform plugin no longer exists, and the JUnitPlatform runner for JUnit 4 is deprecated.

Rather (at a quick glance) the focus would be on a MethodFilter (as you mentioned) and the ConsoleLauncher.