Thanks a lot.
LucasC
You CAN profile an unit test. Creating Performance Session is available in the test result window by right-clicking on the test. It opens up a Performance Wizard. This wizard will create a performace session for you. The default profiling method for unit test is instrumentation.
We DO NOT support profiling a web/load test in Beta2, and we are not planning to support them in RTM/RC either. However, in Whidbey Beta2, Create Performace Session is enabled for whatever test that shows up in the test result window. For all tests other than unit test, bad behavior happens and profiling these tests does not really take you to the result you desire. This is a bug. It will be fixed in RTM/RC. At that time, Create Performace Session will only be enabled for unit test.
I am not very sure if I have answered your question. Please don't hesitate to ask if you have further questions. Thank you for your interest in Profiler!
I don't like to profile the Unit Test itself (or any test itself). I understand that in order to profile my application (Web or Executable) I have to exercise it (execute it in some way). Thanks a lot
So, is there any way to execute my application for profiling purposes but using some of the test to exercise it in order not to play manually with it? I want to profile my application but using some valid test scenarios that I have generate before (that's a way to make it repeatable)
You sure can, LucasC (with unit tests).
After running your unit tests you can go into the Test Results window, right-click on the unit test you want to use as part of your performance session, and select "Create performance session..." from the context menu.
The Performance Wizard will appear allowing you to select how you want to measure performance (sampled or instrumented). Finish off the wizard and then click the Launch button on the Performance Explorer window's toolbar to launch the session with your test.
When the test completes the performance measurements are compiled and displayed.
Tom
http://blogs.msdn.com/ejarvi/archive/2005/04/21/410467.aspx
