This project is read-only.
Project Description
A simple addin to Visual Studio 2012 and Visual Studio 2010, which enables a LoadTest user to be able to give custom name and description for their loadtest.
This is a simple utility that is created as a Visual Studio AddIn. Basically once a load test is completed, you can use this tool/utility to change the "username@machinename timestamp in YYYY-mm-dd" results name that VSLoadTest creates for you to something more memorable that you can remember. Additionally you can also add a small description to go alone with your name that you give for your results.

I personally find giving a custom name and description a easy way to dig through my results, rather than looking at a long list of "username@machinename timestamp pattern"

For e.g. I could call a run as 'Worth Checking for benchmarking', where as for the other runs I can mention it as 'hmmm not a great run'. So after few days when I'm checking the results, I can easily get to the run that I'm interested in. Since there is a brief description too now available, it would make identifying my old runs a little easy.

At least this utility is helpful in my day-to-day VS LoadTest needs, hope it would be of some help to VS LoadTest users out there.

Please Note:
Currently there is no clear way to identify the selected index in the Test Results window offering of Visual Studio. See my question raised with MSDN at: Hence the current work around is to show a list of all the test results and you as a user of the addin will need to select an appropriate test result report name

Also Note
Personally I was not successful in making 1 project code to work for both VS2010 and VS2012. So the current source code works for VS2012 and I will soon publish the installable AddIn for VS2010 separately. Partly the issue with unable to make 1 code to work with both VS2012 and VS2010 is to the fact that .Net 4.0 and .Net 4.5 reference dlls. Even when I try with alias feature and using extern declarations my VS2012 compiles with latest reference DLL instead of VS 10 dll it uses version 11 dll of Common.dll, hence the difficulty. Hopefully I'll find a work around soon enough.

Last edited Oct 30, 2013 at 10:36 AM by ready4operations, version 5