Progress® Telerik® Test Studio® Feedback Portal
Back to Feed
Request a Feature Report a Bug
Declined
Last Updated: 14 Dec 2023 10:01 by ADMIN
ADMIN
Cody
Created on: 14 Feb 2013 21:31
Type: Feature Request
2
Cannot get to TS test properties in VS 2012
In VS 2010 and VS 2008 there was the Test View. From there you can get at a number of Test Studio specific test level settings, such as BrowserType, SilverlightEnabled, etc. There appears to be no equivalent in VS 2012. Test View has been replaced with a Test Explorer, but clicking on a test in Test Explorer does not bring up any test properties. As a result it appears you have no method to get at the Test Studio specific settings in VS 2012.
12 comments
ADMIN
Shtilianov
Posted on: 14 Mar 2014 14:34 
You should be able to include the bad file.vsmdi in any test solution and it will work. You don't really need to have VS2012, in order to add vsmdi file to VS2013. You can just add any empty file with .vmsdi in VS and VS will automatically format it and will open the test list view, from where you can get to the test properties. We agree that this is a workaround and is not the ideal and sustainable solution, we'll be working on a better one.
Ewin
Posted on: 14 Mar 2014 13:55 
I am concerned about others in the future. 

So my concern is now is what if the vsmdi is not available for whatever reason,  I assume that Visual Studio 2013 understands adding a vsmdi because I still have VS 2012 installed and my computer realizes that there is a template from VS 2012 for vsmdi and then uses that template correctly.  But what if a user only has VS 2013 and vsdmi template file is not available and does not know what to do.  

I know that I can make any file with any kind of extension by creating a file in notepad and changing the extension to be what I want it.  The attached vsmdi is my notepad created file
Attached Files:
ADMIN
Shtilianov
Posted on: 14 Mar 2014 08:15 
Here is a short video explaining what I mean: http://screencast.com/t/5XhQAtYbr
ADMIN
Shtilianov
Posted on: 14 Mar 2014 08:01 
Yes the workaround as it's described is a little bit confusing, you don't actually search for the vsmdi file, you just save a new file named "something.msdi" down in the "Name" textbox.
Ewin
Posted on: 13 Mar 2014 14:29 
I don't know if there is a difference between Visual Studio Professional and Ultimate because I have Professional and the screencast below shows exactly what I saw for a project that had the vsmdi file and one that didnt.  The one that did had an error message come up.  

Do I need to do something special to open it properly in Visual Studio 2013?  Considering that for VS 2012, I did not have to do anything special that the above workaround from Pavel so something has changed from 2012 to 2013.  

http://screencast.com/t/CQHMThbrz
ADMIN
Shtilianov
Posted on: 13 Mar 2014 08:46 
VSMDI file is still available in VS2013 at the moment. We'll definitely be looking for a better and more convenient solution for this problem, but at the moment the workaround where you manually add vsmdi file to the solution is still valid in VS2013.
Ewin
Posted on: 12 Mar 2014 17:58 
It has been a while since I looked at this and as Shashi said.  The VSMDI file is not available to add into the solution anymore in Visual Studio 2013.  

To add onto my comment from July 11th, the test explorer in Visual Studio does not have an option to get to the properties of a test.  So this new information supports my suggestion to have the properties adjusted by accessing from the solution explorer.
Shashi
Posted on: 17 Sep 2013 20:49 
I would second Ewin's proposal.  The vsmdi file will eventually be removed (if it hasn't been already in VS2013) - so it is really not a good idea to rely on its functionality.  Better to use something that is expected to stay in future releases.
Ewin
Posted on: 11 Jul 2013 14:34 
Would there be anyway in the future to have the properties show up simply by right clicking on the tstest file and selecting property from the solution explorer?

This workaround is nice, but considering that the test list editor is deprecated so having this ability in the solution explorer is just a little more convienent by a couple clicks
ADMIN
Pavel Kotsev
Posted on: 04 Mar 2013 08:43 
Here is a workaround step by step:

1) Open your solution.
2) From the Solution Explorer right click the solution item.
3) Select Add/New Item
4) Do not click on any of the available items, instead type in the text box 'TestList.vsmdi' or any other item name that ends with '.vsmdi'. Just make sure not to click on any item as it would overwrite your input.
5) Find 'Solution Items' sub folder directly under your solution
6) Double click TestList.vsmdi - this will bring up the 'Test List Editor'
7) Select one of your tests from the 'Test List Editor' right click it and select properties.
8) In the properties pane find all properties of Test Studio tests.
ADMIN
Konstantin Petkov
Posted on: 15 Feb 2013 09:18 
More about the work-around:
http://msdn.microsoft.com/en-us/library/vstudio/jj155802.aspx

Unfortunately I'm having hard time to show properties of the Unit and Coded UI Tests as well. All VS 2012 does is displaying the file properties. Let's hope they can fix that soon.
ADMIN
Daniel Djambov
Posted on: 15 Feb 2013 08:49 
This is new VS2012 behavior - nothing we can do about it for now. VS plan to change this in next VS 2012 patches and then we can figure out how to plug in. 
For now, there is a workaround to create the VS project in VS2010 and add all Test Studio tests in vsmdi test list, then when opening this project in VS2012, there is backwards support to read only see vsmdi lists and selecting Test Studio test from the vsmdi list view will show the properties of the test that are mentioned.
Create an account Log In
View
Type
Status