Looks nice after we have adopted xunit. Trying to compare, does it also support async methods? How about grouping the tests by categories? Does it support fixture like solution? Disposable pattern? And about something xunit doesn't have but mstest1 does: support dll resolving path by runsettings. Does it also support this feature?
while getting the data from the methods using Data Row, is there any naming convention to be followed , how does the test method map the returned data to the parameters of the Test method?
The migration from V1 to V2 is BAD. It is not so easy in a real project with hundreds of tests. MSTest V2 doesn't work with TestSettings file, you must use RunSettings. It doesn't work with DataSource attribute, so you need to implement a code of your own to read the test data and change it in all your tests! It doesn't work with DeploymentItem. A new framework version should UPGRADE the previous framework, not to remove very important features that are used in a lot of projects.
Doesn't talk about writing tests at all, only how to update to v2 and extensibility features.
Extension method
Recursive running test 18:00
DynamicData 21:00
Extending MStest 22:00
Looks nice after we have adopted xunit.
Trying to compare, does it also support async methods?
How about grouping the tests by categories?
Does it support fixture like solution?
Disposable pattern?
And about something xunit doesn't have but mstest1 does: support dll resolving path by runsettings. Does it also support this feature?
while getting the data from the methods using Data Row, is there any naming convention to be followed , how does the test method map the returned data to the parameters of the Test method?
Wish you could do a basic getting started demo, with 1) VSCode 2) Basic .Net Core 5 Console/Web app 3) MS Test 2.
The migration from V1 to V2 is BAD. It is not so easy in a real project with hundreds of tests.
MSTest V2 doesn't work with TestSettings file, you must use RunSettings.
It doesn't work with DataSource attribute, so you need to implement a code of your own to read the test data and change it in all your tests!
It doesn't work with DeploymentItem.
A new framework version should UPGRADE the previous framework, not to remove very important features that are used in a lot of projects.
If anybody can help that ill be great. How to rerun failed test in mstest v2
Kendra is so cute
Hired for her skill, no doubt.
It's good but do not support execution from MTM.
Good stuff. I am glad to see this.
v2: still hot
Can you speak English?