When I create a project for Visual Studio, and import it into our app, when it imports, Visual Studio recognizes the Test Studio tests in the Test Explorer. I can run them with little problems, but if I close out of Visual Studio and re-open it, the Test Studio tests disappear from the Test Explorer and I can no longer work with them as if they were unit tests, though the Test Explorer does find our written unit tests. I can still open the test file in Visual Studio, and the Solution Explorer still shows the Test Studio Project in the Solution. I can still run the tests manually by clicking play, but I can not do anything through the Test Explorer anymore unless I delete all the files of both projects and then recreate them and import the Test Studio VS Project into our VS Solution. Then I can play around with the Test Studio Tests in the VS Test Explorer and gain extra testing functionality, but only for as long as visual studio is open. If I close VS again, then I have to delete the projects and recreate them from scratch again.
I'm using VS 2013, Windows 8.1, Test Studio April 2014. We are building a .NET WPF app. I have about 200+ Test Studio Automated Tests I am trying to import.
I am getting this error on a build and of our solution with the Tests Studio Project included:
========== Load Playlist finished (0:00:00.015626) ==========
------ Discover test started ------
Failed to configure settings for runsettings plugin 'VSTest Run Configuration' as it threw following exception:
'An error occurred while loading the settings. Error: Could not find 'RunSettings' node..'
Please contact the plugin author.
I'm using VS 2013, Windows 8.1, Test Studio April 2014. We are building a .NET WPF app. I have about 200+ Test Studio Automated Tests I am trying to import.
I am getting this error on a build and of our solution with the Tests Studio Project included:
========== Load Playlist finished (0:00:00.015626) ==========
------ Discover test started ------
Failed to configure settings for runsettings plugin 'VSTest Run Configuration' as it threw following exception:
'An error occurred while loading the settings. Error: Could not find 'RunSettings' node..'
Please contact the plugin author.
3 Answers, 1 is accepted
0
Hello Doug,
If I understand correctly, you are creating a Visual Studio solution that has two (or more) projects contained in it, one of them being a Test Studio test project? How does it behave if you keep them in separate solutions?
We had one other customer get the error "Could not find 'RunSettings' node..' Please contact the plugin author". The solution then was to re-install Test Studio. It seems a Visual Studio update somehow damaged our install.
Regards,
Cody
Telerik
If I understand correctly, you are creating a Visual Studio solution that has two (or more) projects contained in it, one of them being a Test Studio test project? How does it behave if you keep them in separate solutions?
We had one other customer get the error "Could not find 'RunSettings' node..' Please contact the plugin author". The solution then was to re-install Test Studio. It seems a Visual Studio update somehow damaged our install.
Regards,
Cody
Telerik
0
Doug
Top achievements
Rank 1
Rank 1
answered on 25 Jun 2014, 03:23 PM
Hi Cody,
Thanks for the reply.
The bug was not as bad as I first reported, however, it does remain after a reinstall of TS.
What I found is, when you relaunch Visual Studio, the tests do not show up in the Test Explorer. However, if I remove the Test Studio Project from the solution, then immediately re-add it, the tests reappear in the Test Explorer. So I don't actually have to delete any files and recreate them.
If I put the projects into different solutions, then the TS tests show up in the test explorer. Now this works for testing out of Visual Studio, but unfortunately, it does not allow me to do code coverage on our application.
I'm not sure if even you guys are aware, but if you put the Test Studio Project into your WPF solution, then Visual Studio Ultimate will give you a code coverage result for your Test Studio Tests. So it is possible to do Code Coverage for Test Studio using only Visual Studio. However, I do need to have the Test Studio Project in the same solution as our application in order to do that.
Thanks for the reply.
The bug was not as bad as I first reported, however, it does remain after a reinstall of TS.
What I found is, when you relaunch Visual Studio, the tests do not show up in the Test Explorer. However, if I remove the Test Studio Project from the solution, then immediately re-add it, the tests reappear in the Test Explorer. So I don't actually have to delete any files and recreate them.
If I put the projects into different solutions, then the TS tests show up in the test explorer. Now this works for testing out of Visual Studio, but unfortunately, it does not allow me to do code coverage on our application.
I'm not sure if even you guys are aware, but if you put the Test Studio Project into your WPF solution, then Visual Studio Ultimate will give you a code coverage result for your Test Studio Tests. So it is possible to do Code Coverage for Test Studio using only Visual Studio. However, I do need to have the Test Studio Project in the same solution as our application in order to do that.
0
Hi Doug,
You may be dealing with a problem that our plug-in is not fully activated yet. Even though you have opened a solution containing a Test Studio project, our plug-in code doesn't get activated until you actually open a test. Any test will do. But until then our code is dormant and the project doesn't fully build.
Make sure you have any test open before you do your build. Let me know whether or not the tests now show up in Test Explorer.
If not then you may have a problem that is specific to your project. Could you send us your project for analysis, or a sample project that reproduces the problem?
Regards,
Cody
Telerik
You may be dealing with a problem that our plug-in is not fully activated yet. Even though you have opened a solution containing a Test Studio project, our plug-in code doesn't get activated until you actually open a test. Any test will do. But until then our code is dormant and the project doesn't fully build.
Make sure you have any test open before you do your build. Let me know whether or not the tests now show up in Test Explorer.
If not then you may have a problem that is specific to your project. Could you send us your project for analysis, or a sample project that reproduces the problem?
Regards,
Cody
Telerik