[
https://issues.apache.org/jira/browse/SUREFIRE-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509399#comment-17509399
]
Tibor Digana commented on SUREFIRE-2037:
----------------------------------------
The next big problem is that we have more and more code but I did not see
integration tests without SPI, means with TestSource - field, directory,
script, etc.
There must be unit tests. I have paid very big attention to cover this project
with unit tests and we should continue with this attitude.
> Allow for surefire-junit-platform's TestMethodFilter to support custom
> TestSources
> ----------------------------------------------------------------------------------
>
> Key: SUREFIRE-2037
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2037
> Project: Maven Surefire
> Issue Type: Improvement
> Components: JUnit 5.x support
> Affects Versions: 3.0.0-M5
> Reporter: Krzysztof Sierszeń
> Priority: Minor
>
> Since JUnit 5 allows for custom {{{}TestSource{}}}s to be configured,
> {{TestMethodFilter}} could provide a way for those sources to be recognized
> and filterable. This way, custom method sources will enjoy the same filtering
> capabilities that method sources do.
> For now, this change specifically targets ArchUnit's {{FieldSource}}, and I'm
> planning to use the solution provided to solve [the following
> issue|https://github.com/TNG/ArchUnit/issues/641].
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
