Test List Editor of VSTS 2010 is deprecated in VSTS 2012

In Visual Studio 2005/2008/2010, we can drag the selected tests from the Test List Editor into the test list. This is a good feature, but it is deprecated in VSTS 2012. The new feature is called Test Explorer.

If you have 1,500+ unit tests in Test List Editor  in VSTS 2010, it is not easy to upgrade those tests in VSTS 2012 because it is deprecated. 

Do you think Test Explorer is user friendly compared to Test List Editor? 

Why Visual studio 2013 doesn't have easy way to run multiple selected webtest/coded web test?

I work in a company which has 100 of client sites and I have coded web tests for all those sites as well as I have couple of coded UI test and load test to verify those sites login and up and running or not  by using visual studio 2010 ultimate, I can easily run all those tests or partial number of tests easily from the Test view or from the Test list editor of VS 2010. Every month during our IT maintenance I run all those web and coded UI tests.

Now I have installed Visual Studio 2013 ultimate, and don't see this incredible feature(test view/test list editor).

I see under load test there are options like run all tests in solution or selected test- from here I can not run easily all those tests(web and coded ui tests) together.  It is very hard to execute all those test from there.

Would you please consider this very important feature to be added in the visual studio 2013 or in the future releases of VS as it helps a lot for the automated tester. I think VS 2010 is much useful for me than VS2012 or VS2013 in this regard.

Thanks and Regards,

Abdur

===

Hi Jaeed,

One workaround is that you could run them in command line:

mstest /TestContainer: WebTest1.webtest /TestContainer: WebTest2.webtest

You could submit this feature request: http://visualstudio.uservoice.com/forums/121579-visual-studio. The Visual Studio product team is listening to user voice there. You can send your idea there and people can vote. If you submit this suggestion, I hope you could post that link here, so other community members who are interested in this issue will help you vote it. If it gets more votes, the product team expert would think about adding it as a new feature in the future product. Thanks for your understanding.

Best Regards,

How to add addtional browsers in Visual Studio 2010

Luckily we can add additional browsers by creating new .browser files in Program Files\Microsoft Visual Studio 10.0\Common7\IDE\Templates\LoadTest\Browsers (Program Files (x86) on 64-bit systems).  The files are simple XML documents that include a name and a few header items such as user agent so there isn’t really anything scary in there.  For example, the definition for IE8 is as follows:

<Browser Name="Internet Explorer 8.0" MaxConnections="6">

  <Headers>

    <Header Name="User-Agent" Value="Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1)" />

    <Header Name="Accept" Value="*/*" />

    <Header Name="Accept-Language" Value="{{$IEAcceptLanguage}}" />

    <Header Name="Accept-Encoding" Value="GZIP" />

  </Headers>

</Browser>

 

Same way you can add other browser like below:

 

Add Internet Explorer 9:

 

<Browser Name="Internet Explorer 9.0" MaxConnections="6">

  <Headers>

    <Header Name="User-Agent" Value="Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)" />

    <Header Name="Accept" Value="*/*" />

    <Header Name="Accept-Language" Value="{{$IEAcceptLanguage}}" />

    <Header Name="Accept-Encoding" Value="GZIP" />

  </Headers>

</Browser>

 

Add Internet Explorer 10:

 

<Browser Name="Internet Explorer 10.0" MaxConnections="6">

  <Headers>

    <Header Name="User-Agent" Value="Mozilla/6.0 (compatible; MSIE 10.0; Windows NT 6.1; Trident/5.0)" />

    <Header Name="Accept" Value="*/*" />

    <Header Name="Accept-Language" Value="{{$IEAcceptLanguage}}" />

    <Header Name="Accept-Encoding" Value="GZIP" />

  </Headers>

</Browser>

 

 

Add Crome 11:

 

<Browser Name="Chrome 11" MaxConnections="6">

  <Headers>   

    <Header Name="User-Agent" Value="Mozilla/5.0 (Windows NT 6.1) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24"/>

    <Header Name="Accept" Value="*/*" />

    <Header Name="Accept-Language" Value="{{$IEAcceptLanguage}}" />

    <Header Name="Accept-Encoding" Value="gzip" />

    <Header Name="Accept-Charset" Value="ISO-8859-1,*,utf-8" />

  </Headers>

</Browser>