-
Notifications
You must be signed in to change notification settings - Fork 20
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
@DisplayName annotation on Test not recognized #21
Comments
I see you did something about this in your fork |
It's one thing to use Support in However, this is is about rendering to XML reporting files which is a totally different story. JUnitXmlTestsListener is what generates those XML files. It receives the same test Events which SBT uses internally to identify tests and modifies the names (which are expected to be a fully qualified class name). e.selector match {
case selector: TestSelector => selector.testName.split('.').last
case nested: NestedTestSelector => nested.suiteId().split('.').last + "." + nested.testName()
case other => s"(It is not a test it is a ${other.getClass.getCanonicalName})"
} Every test annotated with a Then there is SBTs use of those events to identify available tests. Changing the selectors from class names to display names leads to a whole series of changes from where tests are collected to how tests are filtered. Not sure how to proceed on this. |
FWIW, dynamicTest It is correctly shown in |
Once nice feature of JUnit 5 is overriding the outputs of test Method names with more human friendly
@DisplayName
annotation.Seemingly the test output does not pick up the test names from
@DisplayName
but rather just shows the actual method name. Our actual method names are pretty long and not display friendly. The test result xml files should use the@DisplayName
annotation.The text was updated successfully, but these errors were encountered: