Display names of parameterized tests in test explorer
See original GitHub issueAssume we have a pamraterized test test_adding_numbers(a, b)
.
We have parameters [1,2], [2,4], [4,9]
The UI will display the nodes as follows:
Personally I believe it needs to be altered to display just the parameters in the child nodes. I.e. why repeat the function name in the child nodes, we’re testing different parameters and as a user that’s what I would like to see.
Here’s the improved version:
/cc @luabud
More examples of before and after with a larger test base (pytest
repo):
Issue Analytics
- State:
- Created 5 years ago
- Reactions:7
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Display names of parameterized tests in test explorer #4769
Assume we have a pamraterized test test_adding_numbers(a, b). We have parameters [1,2], [2,4], [4,9] The UI will display the nodes as ...
Read more >Change test names for parameterized NUnit in VS Test Explorer
You were close with Name("Chrome") . Instead, the property you want to set in the TestFixture attribute is TestName :
Read more >Visual Studio: Different methods to display unit test - TechNet
Select PlayList, right click in test explorer and select “Add to play list” which will then prompt for a file name. Once this...
Read more >XUnit Parameterized Tests - Test Case Names are all the ...
XUnit Parameterized Tests - Test Case Names are all the same in the Summary ... integrated Test Explorer display the parameters for each...
Read more >Writing parameterized unit tests in C# — Run the same test ...
Note that these test results include a separate line for each set of inputs. I've also added friendly display names to several of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
How do we generate the name for each parameterization?
Personally, I’m +1 on dropping the redundant name as I assume we always have something to list as a name for the parameterization.
I found this really annoying so I’ve implemented this here.