You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For now, we do support JUnit4 parametrized test methods that have a default name, i.e.test[{index}], where test is the name of the test method and index is the index of the parameter used.
However, one can specify a custom name for such test using the annotation value name such as:
"{index}: array = {0}; nothingis {1}"
where variables between curly brackets {...} are replaced by values. For instance, we can have:
0: array = 1; nothingis 2`
There are two issues:
the current implementation of the filter won't recognize such names and test-runner won't find any tests to be run.
test-runner uses classic java command lines to run the test. Providing such names, that contain spaces and path separator ;, would be for now impossible.
The text was updated successfully, but these errors were encountered:
For now, we do support JUnit4 parametrized test methods that have a default name, i.e.
test[{index}]
, wheretest
is the name of the test method andindex
is the index of the parameter used.However, one can specify a custom name for such test using the annotation value
name
such as:where variables between curly brackets
{...}
are replaced by values. For instance, we can have:There are two issues:
test-runner
won't find any tests to be run.test-runner
uses classic java command lines to run the test. Providing such names, that contain spaces;
, would be for now impossible.The text was updated successfully, but these errors were encountered: