-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JUnit5 ParameterizedTest in Container #526
Comments
Example build with JDK 21, Arquillian 1.8.0 on Wildfly 30 - but this is in my opinion irrelevant to the problem. I've tried to debug and gain insight what happens, but had no success. ArquillianExtension.interceptTestTemplateMethod() seems to get called once on the client for each parameter, and then multiple times on the container which seems to indicate that the ParameterizedTestExtension is triggered twice. In general it seems to be more correct if the parameter values are build on the container side, since in more sophisticated variants of @ParameterizedTest the provider code may rely on classes which exists on the container |
This looks like a duplicate of #312 |
yes seems so, #312 is more general in discussing a solution, this is only one aspect which doesn't work when combinining Arquillian & Junit5 Parameterized Tests |
closing |
Issue Overview
Running a Junit5 parametrized test in the container results in repeated execution of all tests as many times as there are parameters provided.
Expected Behaviour
Each test case is only executed once.
Current Behaviour
Steps To Reproduce
a test class like
results in test execution
Additional Information
Test output in IDE or Maven shows that there are 5 executions, which value 1..5. In fact each test is run 5 times which all parameter values again.
RunAsClient executes each test only once.
The text was updated successfully, but these errors were encountered: