Known issues with load testing in Visual Studio 2013

Known issues with load testing in Visual Studio 2013

Rate This
  • Comments 6

We hope you have downloaded  Visual Studio 2013 RTM and started using it to run your performance and load tests. One of the really cool features you should try out is the new cloud-based load testing we have introduced as part of Visual Studio 2013, which lets you generate load to test your app without having to worry about infrastructure setup.

There are some minor irritants/bugs that a few users have reported while using load testing as part of Visual Studio 2013. If you have been affected by any of these issues, we are sorry for the inconvenience. We'll fix these problems at the first possible opportunity. The good news however is that simple workarounds exist for these issues. Here are the list of known issues and the workarounds to fix them.

 

  1. Visual Studio hangs when you try to run a load test on the cloud using Team Foundation Service
    • Issue: Visual Studio hangs when I queue a load test to be run using Team Foundation Service. This is noticed for the first time you try to run a cloud-based load test when there is no active connection to a Visual Studio account from your Team Explorer. You shouldn’t notice this issue in subsequent runs.
    • Workaround: Restart Visual Studio. Go to Team Explorer, connect to a Team Foundation Service account. Then run the load test.

  

  1. Importing results from a cloud-based load test fails the first time
    • Issue: After I run my load test using Team Foundation Service, the 'Download Result' operation fails with the following error: "There was an error while importing the result file. Details: The system cannot find the file specified. After correcting the problem open the results from Load Test Manager".
    • Workaround: This issue is seen in certain cases only for the first time after installation of Visual Studio. Restart the machine and launch Visual Studio again. You will not face this problem.

  

  1. Cannot record web performance tests
    • Issue: I cannot see the web performance test recorder in Internet Explorer, after I upgrade from Release Candidate/Preview build to the RTM version.
    • Workaround 1:  
      1. Close all Internet Explorer windows and Visual Studio.  
      2. Delete the following registry keys
        • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Discardable\PostSetup\Component Categories
        • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Discardable\PostSetup\Component Categories64
      3. Restart Visual Studio and start recording from the web performance test.

 

Once again, we are sorry these issues slipped through and will fix them soon. In the meanwhile, if you notice any new issue or have questions/feedback, please leave a comment.

Leave a Comment
  • Please add 3 and 7 and type the answer here:
  • Post
  • Hi,

    In VS2013 Ultimate "Add Service Reference" dialog after selecting the service when I click the "Advacned..." button I get a message "Index was outside the bounds of the array.".  Is this a bug in VS 2013.  Is there any fix available for this ?

    Thanks

    Madhan

  • Madhan,

    This post is only regarding web performance an load tests. Can you please report this issue using connect.microsoft.com This way you can report it to the right team and track the fix.

    Thanks.

    -Darshan

  • I found that if you copy and paste a web performance test, then modify and attempt to run the new test, it will sometimes run the original source one instead.

  • LoadTest menu is not available when i Open my solution.

    Any Suggestions?

  • Vs2013 Web Test Recorder 12.0 does not work with IE9.  No recording capability whatsoever.  The two work arounds are futile in attempting to record.  Had to go back to VS2012 unless some brilliant person comes up with a solution of how to create a web performance test using IE9.  We will be upgrading in a month or two, but at the moment are standards are set. ;-(

  • So as I look at the past posts, they are dated Nov 2013.  So this Microsoft bug has been around for one full year.

Page 1 of 1 (6 items)