Profiling with ANTS Profiler and MSTest

Posted by Dave Mellors | Filed under Software Development

Had a question today from a customer interested in profiling his unit tests using MSTest which is part of the testing element of Visual Studio Team System. As I hadn’t used MSTest before I decided to take a look and see if you could use it with ANTS Profiler.

After my first attempt at profiling only produced results for MSTest, I suspected that my tests were being run in a seperate process. Luckily MSTest has a /noisolation argument and once I used this everything ran as expected.

http://www.wahooga.com/wp-content/plugins/sociofluid/images/digg_16.png http://www.wahooga.com/wp-content/plugins/sociofluid/images/reddit_16.png http://www.wahooga.com/wp-content/plugins/sociofluid/images/stumbleupon_16.png http://www.wahooga.com/wp-content/plugins/sociofluid/images/delicious_16.png http://www.wahooga.com/wp-content/plugins/sociofluid/images/technorati_16.png http://www.wahooga.com/wp-content/plugins/sociofluid/images/google_16.png http://www.wahooga.com/wp-content/plugins/sociofluid/images/yahoobuzz_16.png http://www.wahooga.com/wp-content/plugins/sociofluid/images/twitter_16.png

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Tags: ,

Permalink | 1 Comment » | May 2, 2007

One Response to “Profiling with ANTS Profiler and MSTest”

  1. Thies Schrader Says:
    December 13th, 2007 at 1:09 pm

    I have been trying to get the same set-up to work – and thank you for the /noisolation which is what stopped me. For those that find this blog and need more details on what to do, here are the arguments ANTS needs to get things rolling;

    .NET desktop application:

    C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\mstest.exe      (or whereever your mstest.exe is located)

    Working Directory:

    c:\Projects\MyProject      (the root folder of your project)

    Agruments:

    /testcontainer:MSUnitTesting\bin\Debug\MSUnitTesting.dll /test:##inserttestnamehere## /noisolation      (note replace ##inserttestnamehere## with the name of the test you want to profile – remove this /test: option to profile everything)

    My next step will be to get ANTS working with TestDriven.Net against my mstest-tests, so I can speed up the time it takes to profile tests.

Leave a Reply

A Perfect