-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Execution of Vintage Tests fail with "displayName must not be null or blank" #2248
Comments
When executing the test using the JUnit Vintage Engine and Surfire using
When executing with
Content of
Content of
|
Reopening for cherry-picking to the release branch. |
Looking forward to test the change 🥇 |
@reinhapa Could you please test against the latest |
@marcphilipp build completed successfully here on my local system.. |
Prior to this commit, `VintageTestDescriptor` used the `Description`'s method name when it wasn't null. However, there are edge cases where it can be empty which lead to blank display names which are not allowed by the Platform. Thus, it is now only used if not blank. Fixes #2248.
Cherry-picked on documented on the release branch. |
Steps to reproduce
Execute the build https://github.com/reinhapa/exist/tree/junit5 using:
mvn -T 2C -Ddocker=false test -B -e
Context
3.6.3
5.6.1
3.0.0-M4
Deliverables
Test should run as before using JUnit
4.13
The text was updated successfully, but these errors were encountered: