Usually you will endup with one engine and one or more test APIs.
The documentation above solves all combinations with junit4, junit5 and
testng.
If somebody uses one @Test annotation and wants to say that f/w1 should run
test class 1 but f/w2 should run test class 2, then the plugin should be
conf
Hi Slawomir,
Pls follow this page
https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-platform.html
There is a chapter "How to run multiple APIs or Engines". There are also
some links pointing to our integration test in the Apache project.
Pls have a look.
Cheers
Tibor
On W
Hi,
I understand the difference between framework and providers.
I also know that we can add specific providers as dependency to the plugin
and in the result we have manually selected providers.
When we don't configure any dependency the provider is chosen automatically
depending on what we have
Hi Slawomir,
The reality is different.
It's not the frameworks but providers.
So the plugin iterates over providers.
You may choose whether you will define the provider artifacts in plugin
deps or you let the plugin to select the providers upon dependencies which
means that there is some logic and
Hi all,
to complete Sławomir description, the rational of Slack proposal to run it
instead of adding a new toggle to just fail is that the logic to detect the
described case is exactly the same so when we have detected that, either we
fail with the new toggle + ignore it by default or we try to ru
Hi,
When multiple test frameworks are present on project classpath surefire
chooses one framework for running the tests.
In such situations, some tests are silently skipped.
I've created issue [1] for it with a simple proposition.
After discussion on slack another proposition was in place to d
