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
The reason why current implementation put the display name as the description part is that: the display name can only be resolved at the runtime. So, we have to show the method declaration name at first before the test case runs.
It would be nice, if the TEST RESULT (which I understand that it is generated after execution) is able to display the JUnit 5 display name instead.
Especially it may be enhanced to display as the fancy and colorful thing in the future. Credit: baeldung
└─ Display name generator unit test ✓
├─ A number is buzz... ✓
│ ├─ A number is buzz if it is one of the following numbers. ✓
│ │ ├─ Number 5 is buzz. ✓
│ │ ├─ Number 10 is buzz. ✓
│ │ └─ Number 20 is buzz. ✓
│ └─ A number is buzz if it is divisible by five. ✓
└─ A number is fizz... ✓
├─ A number is fizz if it is one of the following numbers. ✓
│ ├─ Number 3 is fizz. ✓
│ ├─ Number 12 is fizz. ✓
│ └─ Number 18 is fizz. ✓
└─ A number is fizz if it is divisible by three. ✓
Hi Sheng Chen (@jdneo), I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
Activity
jdneo commentedon Aug 11, 2023
Referenced from #1595
charleech commentedon Aug 11, 2023
It would be nice, if there is an execution time for each method/sub-group/group, especially support for JUnit5 parallel.
github-actions commentedon Nov 13, 2025
Hi Sheng Chen (@jdneo), I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
Leverage VS Code 1.80’s new terminal output support: tests printed to the integrated terminal now show clickable file links. See https://code.visualstudio.com/updates/v1_80#_terminal-output-support
If you prefer the Debug Console (which already supports clickable stack traces), add:
Reference: clickable stack trace in java debugger output vscode-java-debug#798 (comment)
For trimming or simplifying test messages in the Test Results view:
• Simplify the test message: Simplify the test message #1393
• Hide/shorten JUnit call stacks via a regex setting proposal: [Request] Hide the JUnit Callstack from the stacktrace #1281
The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!