VS2010 Ultimate Web Testing Silverlight - playback suceeds but doesn't do anything

Question

Hi All,

I am using Visual Studio 2010 Ultimate to perform web tests against a Silverlight 4 application. I have the web and load test plugin from http://teamtestplugins.codeplex.com/releases/view/43166 installed.

I record a web test where I go into the Silverlight application and press a button to queue a job. When the job is queued, its status will appear as such. So I can go into the application from a different machine and view the same page and the job status will appear as queued.

The problem is, when I play the web test, which should requeue the same job, and manually check the job status, it does not update its status to queued. The web test results appear that it has succeeded (200 OK) but I know that it's not doing what I want it to because the job is not being queued.

The most important part of this web test is that it clicks a button which queues a job. When I replay the web test, it doesn't click that button and the job does not get queued.

Is there a solution to this problem?

Answer 1

Hi, the web tests just replay the http calls so you might not see the button being clicked.

Can you also try to capture the requests via fiddler when you record the test vs when you replay the test and compare them.

You can also generate the web test from the fiddler trace http://www.fiddler2.com/fiddler/help/WebTest.asp

Thanks,

Anuj

---

http://www.anujchaudhary.com

Answer 2

Thank you for the response, Anuj.

While I won't observe the button being pressed, I do expect to see the job being queued as that's what clicking the button does. My ultimate goal with this web test is to queue up the job.

Do you mean run fiddler while recording the web test? I have tried to generate the web test with fiddler alone and that has proved unsuccessful.

Thank you,

Rei

Edit: When I try to record it with Fiddler running, I noticed that when I click the button, Fiddler does not record anything. Fiddler also records a lot less requests than Visual Studio.

Answer 3

Hi, you should see that the job is queued if the playback was correct. To verify that the playback was correct, can you compare the fiddler trace when you perfrom the actions on the site manually with the trace when the web test is run.

Thanks,

Anuj

---

http://www.anujchaudhary.com

Answer 4

Hi Anuj,

Yes, that's the problem, the job is not being queued. Fiddler does not trace anything when I do press the button to queue the job. Comparing VS and Fiddler's trace, VS captures a lot more things actually. I am using Fiddler2 with the default settings. Are there any special configurations for Fiddler when dealing with Silverlight?

Thanks,
Rei

Answer 5

Hi Rei,

Thank you for posting in the MSDN forum.

I would like to know that what technology you use to queue a job. If a request is not sent to the  server when you click a button and queue the job, the web test recorder can’t record anything. So the job will not be queued.

Thanks,

---

Amanda Zhu [MSFT]
MSDN Community Support | Feedback to us

Answer 6

If you dont see any http requests being captured, then web test will not playback it for you since it only works for http request.

You can consider using coded ui tests.

Thanks,

Anuj

 

---

http://www.anujchaudhary.com

Answer 7

Hi All,

Amanda,

It uses HTTP GET/POST requests. I believe the data being sent and received is encoded in msbin1 format. Would there be any special tweaking to get VS to send the proper request?

Anuj,

Fiddler is not capturing the http requests when I queue the job. Visual Studio however, does capture the http requests. However, when I play back the web test from Visual Studio, the job is not being queued. Coded UI Tests are not an option because the goal is load testing.

Regards,
Rei

Answer 8

Hi Rei,

As Anuj said, if any HTTP requests are captured, the web test will play back it. If the playback is correct, you will see the job is queued. Your current situation is so strange. Actually you can create a coded UI test for your application to just run to check if the job can be queued. If the job is still not queued, I think that maybe Visual Studio does not capture the HTTP requests.

Best regards,

---

Amanda Zhu [MSFT]
MSDN Community Support | Feedback to us

Answer 9

You can get a 200 OK when the request actually has failed. You may need to add a validation rule that looks for the text "Fault" in the response to the request. If you do have a fault then you need to look at the response with the web editor plugin and see what the error is....

Thanks!

Ken

Answer 10

You might want to check out this plugin to see if it helps: http://blogs.msdn.com/b/edglas/archive/2010/08/07/plugins-for-handling-json-and-msbin1-silverlight-payloads-on-codeplex.aspx

Answer 11

Hi Rei,

What about your issue now? Have you resolved it? And does MatthewSullivan and Kabaker551111's suggestion help you?

Would you mind letting us know the result of the suggestion?

Thanks,

---

Amanda Zhu [MSFT]
MSDN Community Support | Feedback to us

Answer 12

Hi Amanda,

Unfortunately, my issue remains unresolved. I was not able to find "Fault" in the reponse of the request and installing the plugin does not fix the problem.

Regards,
Rei

Answer 13

Rei,

Installing the Web test editor plugin (if that is what you are talking about) will not "fix" the problem, but rather let you see that the "Fault" message is there. See the pics below.....

Answer 14

Hi Ken,

I searched through all the requests using Ctrl+F but could not find a Fault. I do not believe this is the error.

What I did notice is that the playback render in the web test shows that Silverlight is not installed and it asks me to install it (it's installed on my browser of course). From what I've read on these forums that is normal for web tests to give that feedback when testing Silverlight applications.

Regards,
Rei

Answer 15

Hi Rei,

In order to gain the detailed information, you can capture the recording log for pages to see what the server is sending. Then carefully compare it with what is getting sent in the web test by looking at the request headers and body for the request.

Here is a help link about how to enable VSTS logging:

http://blogs.msdn.com/b/yutong/archive/2006/10/03/how-to-enable-vsts-logging_3f00_.aspx

In addition, there is a good article that you can go through in detail and try some of the advanced setting and trouble shooting techniques:

http://blogs.msdn.com/b/edglas/archive/2007/12/02/web-test-authoring-and-debugging-techniques-for-vs-2008.aspx

Best regards,

---

Amanda Zhu [MSFT]
MSDN Community Support | Feedback to us

Answer 16

I've never gotten trl+F to work for me. What I do instead is set a validation rule that looks for the text "Fault" in the response body. Then it flags it as a failed url so you can then look at it with the web editor plugin.

Thanks!
Ken