We have great news! We still haven't implemented it! But that's not the great news (I mean, what's so great about that?).
What is great is that we have our "Profile next application" feature (see here
). Using this feature you could easily attach the profiler to any executable that is just about to be started. For example, if you're using MSTest for testing, then all you need to do is "Profile next application" with a file name of "QTAgent" (for VS2012 without test settings use "vstest.executionengine"). This will make JustTrace attach to the unit test runner and eventually give you a performance profile of the test run. The only ingredient here is knowing the name of the test runner's process. If you run into trouble with that, then don't hesitate to contact us again.
This will, in principle, give you unit test profiling, both performance and memory.
The other piece of good news is that we're actively working on integrating JustTrace with JustCode's unit test runner. You will be able to profile tests right from the JustCode test runner at most by Q3 SP1's release.
Have a nice day!
Share what you think about JustTrace & JustMock with us, so we can become even better! You can use the built-in feedback tool inside JustTrace, our forums
, or our JustTrace