Membru care solicită informaţii
These three papers are must-read for anyone working with Web tests. If your Web tests are failing, read these posts to learn about what you are doing before posting to the forum.
Also see Sean's blog post, Debugging Web Tests, which walks through debugging a web test using VS 2005. The experience is much improved in VS 2010, as is shown in this walkthrough from the 2010 paper.
18 decembrie 2007 19:13
- Editat de Ed GlasMicrosoft employee, Moderator 3 aprilie 2010 13:40
Your link to the 2010 article is broken. It's pointing to http://social.msdn.microsoft.com/edglas/archive/2010/03/24/web-test-authoring-and-debugging-techniques-for-visual-studio-2010.aspx.
The actual link found by manually browsing from your blog is: http://blogs.msdn.com/edglas/archive/2010/03/24/web-test-authoring-and-debugging-techniques-for-visual-studio-2010.aspx.
-John1 aprilie 2010 17:38
really helpful write up.
Thanks a lot Ed.
Just that, I found your posted code are cut. E.g., I can only see
[Description("Adds extraction rule for Report Session and binds this to querystri
In your sample recorder plugin code. All other long lines cut to the same spot as well.
Strange nobody say anything for so long. Maybe it's only me. Will try a different machine tomorrow.
Another important question, Ed or anyone,
How do you debug your Web Test Plugins? Including but not limited to recorder plugin, Custom Validation Rule, and Custom Extraction Rule?
You play up the recording to certain point, then all of sudden hold up the http traffic and start debugging, viewing returns, and play with the code?
Thanks16 martie 2012 01:32
We are in progress of migrating from Load Runner to VS2010 However we encounterd two issue mentioned below for same I need your thoughts.
1. How to monitor UNIX servers conuters through VS2010 Load test
2. How to Call WSDL file to hit the webservices in load test.
Thanks in Advance,
Naveen23 martie 2012 09:15
I think it's best to store the plugins in a class library of their own so they can be used across multiple web test projects without having to copy and paste each time you need them, just reference their bin folder for the latest version.
For debugging the web test plugins the best way I have found the best way to do this is to go to the solution where the web tests are stored and add an existing project to that solution. I think that just links the class library with the test solution so any changes made to the class library will be updated in any solution referencing it. Once it's part of the solution using Debug mode in the web test and breakpoints in the class code looks to work OK.
I've only tried this with a Web Test plug-in and a Web Test Request plug-in but I expect the method is the same for any plug-in.17 aprilie 2012 08:17
To test web services you should have a look at http://msdn.microsoft.com/en-us/library/ms182557(v=vs.100).aspx
You can also download http://wcfloadtest.codeplex.com/ from the ALM Rangers on codeplex.
That should give you more than enough capability to test your web service elements or add them within your web tests. I've used the wcfloadtest myself against SignalR and web services in the past.
With regard to monitoring Unix machines. http://social.msdn.microsoft.com/Forums/en-US/vstswebtest/thread/4153429d-90b9-4624-8a59-ae73149c17d0/]
SCOM might be the answer if you can talk to one of your operations guys or set it up yourself for your test environment.
In my experience if you monitor the machines with what will be your operational monitoring solution it helps progress through OAT and fine tune your alerting for performance issues.
Hope that helps.18 octombrie 2012 07:05