Hi,
I'm quite new to Test Studio but have had some moderate success early on. I am testing an ASP.NET web application which is a Point of Sale (POS) system. I have successfully recorded a test which logs in, adds some products to an order, fulfils part of the order, takes a payment, and closes the sale.
I can re-run that test perfectly. The browser spins up and I see the various steps occur and then I see the new sale in the sales report.
I have now used that test as the basis for a Load Test but I am not getting what I expected, and I think perhaps what I need and what's being provided are not the same. I need to simulate 10 concurrent users processing that sale. I need that test run in 10 separate threads in one go. What I get though is no browsers popping up and no new sales being created in the database.
There is no indication of failure, but nothing seems to be "happening". If I run the single test manually and I see the browser come up, I can see the CPU sits between 40% and 50% for the duration of the test. If I run the Load Test as a single user the CPU activity never gets this high. Something is wrong.
So, can someone explain if what I expect of Load Test and what it does are actually not the same..? I would have expected 10 browser windows to open up and 10 new sales to go into the database, but what I get instead is nothing. The "steps" appear to have been reduced to a series of HTTP requests.
Anyway, some advice would be much appreciated.
Kind regards,
Jack
I'm quite new to Test Studio but have had some moderate success early on. I am testing an ASP.NET web application which is a Point of Sale (POS) system. I have successfully recorded a test which logs in, adds some products to an order, fulfils part of the order, takes a payment, and closes the sale.
I can re-run that test perfectly. The browser spins up and I see the various steps occur and then I see the new sale in the sales report.
I have now used that test as the basis for a Load Test but I am not getting what I expected, and I think perhaps what I need and what's being provided are not the same. I need to simulate 10 concurrent users processing that sale. I need that test run in 10 separate threads in one go. What I get though is no browsers popping up and no new sales being created in the database.
There is no indication of failure, but nothing seems to be "happening". If I run the single test manually and I see the browser come up, I can see the CPU sits between 40% and 50% for the duration of the test. If I run the Load Test as a single user the CPU activity never gets this high. Something is wrong.
So, can someone explain if what I expect of Load Test and what it does are actually not the same..? I would have expected 10 browser windows to open up and 10 new sales to go into the database, but what I get instead is nothing. The "steps" appear to have been reduced to a series of HTTP requests.
Anyway, some advice would be much appreciated.
Kind regards,
Jack
3 Answers, 1 is accepted
0
Hi Jack,
What I get though is no browsers popping up...
When running a Test Studio Load Test this is normal. Load tests don't use an actual browser. They send pre-recorded HTTP requests directly on the wire at your web server.
...and no new sales being created in the database.
Now this is unexpected. Because the load test is sending HTTP requests, exactly like a real browser does, we would expect something to happen on the back end. I can help diagnose this but I need the following items:
Once I have all this information I should be able to diagnose why it's not working as expected.
Regards,
Cody
Telerik
What I get though is no browsers popping up...
When running a Test Studio Load Test this is normal. Load tests don't use an actual browser. They send pre-recorded HTTP requests directly on the wire at your web server.
...and no new sales being created in the database.
Now this is unexpected. Because the load test is sending HTTP requests, exactly like a real browser does, we would expect something to happen on the back end. I can help diagnose this but I need the following items:
- A copy of the load test. This will be a .tstest file on disk.
- A Fiddler trace of the load test running starting and ending with only one VU. NOTE: If your application uses HTTPS please be sure to check "Decrypte HTTPS traffic" else Fiddler will not capture the load test traffic.
- A Fiddler trace of you doing the same thing manually in a browser, not using Test Studio at all.
- The log from the load agent.
Once I have all this information I should be able to diagnose why it's not working as expected.
Regards,
Cody
Telerik
0
Jack
Top achievements
Rank 1
Rank 1
answered on 19 Feb 2014, 09:01 AM
Thanks Cody. Let me know if there's anything else you need for diagnosis.
0
Hi Jack,
I am concerned about the session highlighted in the attached screen shot. Instead of getting the expected response, the web server simply closed the connection without sending any response at all. It implies that the server did not like the request and therefore refuses to answer.
Can your web developers help figure out why the web server refused to respond? If we can figure this out then we'll know what to do next.
Regards,
Cody
Telerik
I am concerned about the session highlighted in the attached screen shot. Instead of getting the expected response, the web server simply closed the connection without sending any response at all. It implies that the server did not like the request and therefore refuses to answer.
Can your web developers help figure out why the web server refused to respond? If we can figure this out then we'll know what to do next.
Regards,
Cody
Telerik