ux: Improve the experience showing the JUnit4's parameterized tests#1302
Merged
ux: Improve the experience showing the JUnit4's parameterized tests#1302
Conversation
jdneo
force-pushed
the
cs/issue-1296
branch
from
f6aafed to
f4cdf5d
Compare
Eskibear
approved these changes
Sep 22, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix #1296
Now when running JUnit4's parameterized tests, the appearance is like what it is in Eclipse:
Example 1
Example 2
Please note that the error message will only appear if triggering the test from the class level.
This is a limitation of VS Code, if a test run does not append results to the trigger item or its children, the test message will not show.