Hello,
Just a few questions on load testing and actual test making.
1. For Load Testing I've read the document/guide of test studio but still confused about how the charts for Complete/Faulted Virtual Users works. We used 600 users but the chart goes into the 900s or even thousands in the case of Faulted users. Why is this? Do the users simply restart the process once they complete their first attempt?
2. For a standard website test we are creating a new item, going in and editing its contents and then going back to the list to delete it (restoring it back to original state). The problem we are experiencing is the link to the item (name: viewLink) seems to be changing its element name when we come back to the list to to delete it (changing to viewLink1 or viewLink2) causing it to return the element not found error. Of course there are no other items being made at this time to make it move down the list (it is always the 1st item) but is there another route to take in order for the test to determine which element is being clicked on?
Thanks
Just a few questions on load testing and actual test making.
1. For Load Testing I've read the document/guide of test studio but still confused about how the charts for Complete/Faulted Virtual Users works. We used 600 users but the chart goes into the 900s or even thousands in the case of Faulted users. Why is this? Do the users simply restart the process once they complete their first attempt?
2. For a standard website test we are creating a new item, going in and editing its contents and then going back to the list to delete it (restoring it back to original state). The problem we are experiencing is the link to the item (name: viewLink) seems to be changing its element name when we come back to the list to to delete it (changing to viewLink1 or viewLink2) causing it to return the element not found error. Of course there are no other items being made at this time to make it move down the list (it is always the 1st item) but is there another route to take in order for the test to determine which element is being clicked on?
Thanks
1 Answer, 1 is accepted
0
Hello,
A virtual user can either be "Completed" or "Fault" but not both. A "Completed" virtual user is one that successfully ran through all the steps contained in the User Profile.
A "Faulted" virtual user is one that got part way through the steps ran into some abnormal unrecoverable error and aborted.
We used 600 users but the chart goes into the 900s or even thousands in the case of Faulted users. Why is this? Do the users simply restart the process once they complete their first attempt?
Yes, specifying 600 VU's doesn't mean run 600 VU's and then stop, it means maintain a constant load of 600 VU's for the entire duration of the test. When a VU completes or faults it starts over again at the top of the User Profile. Thus it's very normal and expected for the Completed users to be far greater than 600. If you have less than 600 it's an indicator you didn't give the test enough time to run.
For item 2) I'm sure there's a much smarter way to handle this scenario. First try following this guideline for how to handle dynamic ID's. If that doesn't help, please create a new separate support ticket on this problem. It gets too confusing too quickly trying to work multiple unrelated issues in the same ticket at the same time. Before you submit your ticket, please go to Step Failure Details, find and click Export then attached the .zip file created. It will contain a lot of useful detailed information that can help us diagnose such problems.
Regards,
Cody
Telerik
A virtual user can either be "Completed" or "Fault" but not both. A "Completed" virtual user is one that successfully ran through all the steps contained in the User Profile.
A "Faulted" virtual user is one that got part way through the steps ran into some abnormal unrecoverable error and aborted.
We used 600 users but the chart goes into the 900s or even thousands in the case of Faulted users. Why is this? Do the users simply restart the process once they complete their first attempt?
Yes, specifying 600 VU's doesn't mean run 600 VU's and then stop, it means maintain a constant load of 600 VU's for the entire duration of the test. When a VU completes or faults it starts over again at the top of the User Profile. Thus it's very normal and expected for the Completed users to be far greater than 600. If you have less than 600 it's an indicator you didn't give the test enough time to run.
For item 2) I'm sure there's a much smarter way to handle this scenario. First try following this guideline for how to handle dynamic ID's. If that doesn't help, please create a new separate support ticket on this problem. It gets too confusing too quickly trying to work multiple unrelated issues in the same ticket at the same time. Before you submit your ticket, please go to Step Failure Details, find and click Export then attached the .zip file created. It will contain a lot of useful detailed information that can help us diagnose such problems.
Regards,
Cody
Telerik