-
Notifications
You must be signed in to change notification settings - Fork 48
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
Use mstestv3 as testing framework #372
Use mstestv3 as testing framework #372
Conversation
This pull request introduces 1 alert when merging cc89db9 into 31a186b - view on LGTM.com new alerts:
|
8a7ee69
to
dc9669e
Compare
5be975c
to
57b371a
Compare
@@ -79,7 +58,7 @@ | |||
// do verification ... | |||
if (XmlReader == null) | |||
{ | |||
XmlReader = XmlReader.Create(this.TestContext.TestDeploymentDir + "\\NotificationMethodGeneratorTestCodeSnippets.xml"); | |||
XmlReader = XmlReader.Create("NotificationMethodGeneratorTestCodeSnippets.xml"); |
Check notice
Code scanning / CodeQL
Static field written by instance method Note
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Note: mstest v2 have some serious problems when multiple projects use DeploymentItem so it will always fail if running booth "Tools" tests from within VS.
This pr is quite old,. the support is now better so want to se how it works in devops.
Maybe mstestv2 can be used for all projects except tools tests ??