Skip to content
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

Improve the test results view #1588

Open
jdneo opened this issue Jul 7, 2023 · 2 comments
Open

Improve the test results view #1588

jdneo opened this issue Jul 7, 2023 · 2 comments

Comments

@jdneo
Copy link
Member

jdneo commented Jul 7, 2023

See: https://code.visualstudio.com/updates/v1_80#_terminal-output-support

@jdneo
Copy link
Member Author

jdneo commented Aug 11, 2023

Referenced from #1595

Regarding to the #1466

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.

001

002

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. ✓

@charleech
Copy link

It would be nice, if there is an execution time for each method/sub-group/group, especially support for JUnit5 parallel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants