[
https://issues.apache.org/jira/browse/SUREFIRE-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17446656#comment-17446656
]
Tibor Digana commented on SUREFIRE-1954:
----------------------------------------
[~slawekjaranowski] Can you please rewrite the description? It does not match
the reality of the implementation. We did not implement the option
*failOnMultipleFrameworks*.
> Fail on multiple test framework
> -------------------------------
>
> Key: SUREFIRE-1954
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1954
> Project: Maven Surefire
> Issue Type: New Feature
> Reporter: Slawomir Jaranowski
> Assignee: Tibor Digana
> Priority: Major
> Fix For: 3.0.0-M6
>
>
> When multiple test frameworks are present on project classpath surefire
> chooses one framework for running test.
> During automatically provider discover some of type test can be *skipped*
> without any knowledge and information for developer.
> It is danger situation than developer can add *second* test framework to
> project and in the result some of test will be *skipped silently.*
> We can force usage one or more needed providers by adding those to plugin
> dependency and we can have control on executing test.
> h3. Proposition
> - add options {{failOnMultipleFrameworks}} *false* by default
> h3. Scenario 1 - default
> h4. when
> - {{failOnMultipleFrameworks = *false*}}
> - many tests framework on classpath
> - no providers on plugin dependency
> h4. then
> - current behavior - choose first provider with warning about skipped elses
> h3. Scenario 2
> h4. when
> - {{failOnMultipleFrameworks = *true*}}
> - many tests framework on classpath
> - no providers on plugin dependency
> h4. then
> - fail plugin execution with reason
> h3. Scenario 3
> h4. when
> - many tests framework on classpath
> - selected providers on plugin dependency
> h4. then
> - ignore {{failOnMultipleFrameworks}}
> - use providers from dependency list, no warning
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
