I created a load test and was finally able to run it. It is simply a user logging in to the web site via https and then log out. The web application adds a record to the database each time a user logs in.
After I ran the load test, I reviewed the database table, I did not see any records in the database for the users that I used. The load test did not indicate any errors. I am puzzled. Please help!
After I ran the load test, I reviewed the database table, I did not see any records in the database for the users that I used. The load test did not indicate any errors. I am puzzled. Please help!
2 Answers, 1 is accepted
0
Accepted
Hi Maria,
I'm sorry to hear you're having problems with this.
It sounds like your VUs are not getting the job done. Here's what happens when you run a Load test:
Your virtual guys go through a list of HTTP requests sending each on to the server. They do that even if the server is down. Occasionally they might hit TCP/IP errors. This doesn't stop them but Test Studio notices that.
When a VU hits an TCP/IP error it's listed as a Faulted User - a user that couldn't complete his task. Faulted Users is a parameter you can monitor along with Created users, response time etc.
http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/load-testing.aspx
So rerun your test and follow the number of Faulted Users closely. If you have the same number of Faulted users and Created users - we would know something is up and the users are not getting the job done. From there it's a question on troubleshooting where the workflow is breaking down.
The Dynamic targets might be the first thing you should check if a problem is present:
http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/load-testing/designing-load-tests/load-dynamic-targets.aspx
I hope this helps.
Greetings,
Stoich
the Telerik team
I'm sorry to hear you're having problems with this.
It sounds like your VUs are not getting the job done. Here's what happens when you run a Load test:
Your virtual guys go through a list of HTTP requests sending each on to the server. They do that even if the server is down. Occasionally they might hit TCP/IP errors. This doesn't stop them but Test Studio notices that.
When a VU hits an TCP/IP error it's listed as a Faulted User - a user that couldn't complete his task. Faulted Users is a parameter you can monitor along with Created users, response time etc.
http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/load-testing.aspx
So rerun your test and follow the number of Faulted Users closely. If you have the same number of Faulted users and Created users - we would know something is up and the users are not getting the job done. From there it's a question on troubleshooting where the workflow is breaking down.
The Dynamic targets might be the first thing you should check if a problem is present:
http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/load-testing/designing-load-tests/load-dynamic-targets.aspx
I hope this helps.
Greetings,
Stoich
the Telerik team
Are you enjoying Test Studio? We’d appreciate your vote in the ATI automation awards.
Vote now
Vote now
0
Maria
Top achievements
Rank 1
Rank 1
answered on 29 Oct 2012, 07:11 PM
Thanks for the prompt response. Once I unchecked all the dynamic target checkboxes, the login portion of the script appeared to be working and the Faulted Virtual Users return 0.