apache / apache/maven-surefire
[SUREFIRE-1736] JUnit 5 runner does not evaluate display names of nested tests
- Dominant language
- Java
- Stars
- 461
- Forks
- 588
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 19
Description
**[Dietrich Schulten](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dschulten)** opened **[SUREFIRE-1736](https://issues.apache.org/jira/browse/SUREFIRE-1736?redirect=false)** and commented
https://issues.apache.org/jira/browse/SUREFIRE-1546 introduced support for JUnit5 DisplayName annotations.
It seems however that display names on `@Nested` test classes are not evaluated yet.
---
**Issue Links:**
- [SUREFIRE-1546](https://issues.apache.org/jira/browse/SUREFIRE-1546) JUnit 5 runner does not honor JUnit 5 display names
Contributor guide
Research direction
Start by reading SUREFIRE-1546 and comparing its JUnit 5 display-name support with the runner's handling of @Nested test classes. Done means display names declared on nested test classes are evaluated and used by the runner.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100