apache / apache/maven-surefire
[SUREFIRE-1337] Add support for additional JUnit Platform selectors and filters
- Dominant language
- Java
- Stars
- 461
- Forks
- 588
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 19
Description
**[Marc Philipp](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=marcphilipp)** opened **[SUREFIRE-1337](https://issues.apache.org/jira/browse/SUREFIRE-1337?redirect=false)** and commented
The JUnit Platform provider currently supports includeTags and excludeTags as synonyms for groups and excludeGroups. The JUnit platform supports additional filters, e.g. for engines and packages. Moreover, it supports selectors for URIs, local files, local directories, packages, classes, methods, and classpath resources.
It would be great if we could add support for these selectors and filters to the provider via custom configuration properties, e.g. like this:
```xml
maven-surefire-plugin
2.19.1
com.acme.foo
com.acme.bar
foo, bar
acceptance, integration
org.junit.platform
junit-platform-surefire-provider
${junit.platform.version}
```
---
No further details from [SUREFIRE-1337](https://issues.apache.org/jira/browse/SUREFIRE-1337?redirect=false)
Contributor guide
Research direction
Start by locating the JUnit Platform provider in Maven Surefire and the configuration handling for the existing includeTags and excludeTags support. Review the JUnit Platform selectors and filters named in the issue, then identify how each should map to custom properties. Done means the requested selectors and filters are supported and covered by provider tests, but the issue supplies no file or test names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100