4.5 MSTest and dotTrace 3.1

I am stoked by the native MSTest support in 4.5. It is working flawlessly for me.

I am now trying to profile a test using dotTrace 3.1. When I click profile for a test it runs the test, opens dotTrace and loads the snapshot but the snapshot seems to be profiling the TestRunner itself and not my test?

See image below. This is what it shows me in dotTrace no matter what test I profile (even when trying to profile the entire TestClass)

dotTraceAndReSharper45.png

9 comments

Anyone have any ideas?

Not sure why the image I posted shows up blurred (I am assumming it is part of the forum rules?)

But if you click on the image you can see it clearly.

0

Hello,

I'm afraid that dotTrace integration has not been updated to support the
MS Test model. Previously it would profile the satellite process we use for
running the tests, and that was OK. With MSTest, this satellite process is
spawning a new one to actually run the tests, so the profiler only sees the
test runner code.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0

Thanks for the response.

are there any plans to update dotTrace to have MS Test support? Is this something coming in dotTrace 4.0?


Thanks

0

Hello,

are there any plans to update dotTrace to have MS Test support?


Surely there are! It's very unfortunate we got the features in two products
misaligned this way. It has to be fixed.

Is this something coming in dotTrace 4.0?


R# unit testing and dotTrace teams have not ruled this out yet. I think they'll
drop a note when this is known.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0

Same problem here...
Is there any workaround? Is it possible to trace MS Tests via dotTrace?

0

I am also suffering with this limitation.  I'm running the latest version of dotTrace and latest release ReSharper.  Coupld we please have an update on this feature?  It is very important to me in serveral projects.

Thanks.

0

When dotTrace spins up mstest.exe, it needs to pass the -noisolation switch. This switch gets mstest.exe to run the tests within it's own process/appdomain. The default behaviour is to run the tests outside of the mstest.exe appdomain (or process I can't remember which) to give it some protection.

0

Sorry, should have been /noisolation.

0

Hello Jeffrey
     Does this happen with build #1289 (from http://www.jetbrains.net/confluence/display/ReSharper/ReSharper+4.5+Nightly+Builds) as well?

Andrey Serebryansky

Support Engineer

JetBrains, Inc

http://www.jetbrains.com

"Develop with pleasure!"

0

Please sign in to leave a comment.