Load Testing not firing any Time Outs

Question

Hi,

    I have recorded a Scenario using Web Perfomance test and then conducted load test for 250 users using Visual Studio 2010. 

    The test is giving a Average Response time of 64s. Actually a timeout should occur if the loading time is greater than 60 seconds. 

    This is a silverlight application. The time out occurs while I am running the project. But while load testing even after getting a response 

     time greater than 60 seconds it's not showing any time outs. Why time outs are not showing? What should I do to show time outs?

     Any help will be appreciated. I am new to this field

Answer 1

Hi,

I have recorded a Scenario using Web Perfomance test and then conducted load test for 250 users using Visual Studio 2010. 

The test is giving a Average Response time of 64s. Actually a timeout should occur if the loading time is greater than 60 seconds. 

This is a silverlight application. The time out occurs while I am running the project. But while load testing even after getting a response 

time greater than 60 seconds it's not showing any time outs. Why time outs are not showing? What should I do to show time outs?

Any help will be appreciated. I am new to this field.

Answer 2

Hi PhilipMG,

Thank you for posting in the MSDN forum.

Would you mind letting us know more information? What is the result if you just run your web test? What is your load test result now? Do you mean that you set the Test Timeouts with the following steps?

Open LocalTestRun.testrunconfig->Test Timeouts.

If so, setting time limits for tests and test runs has these effects:

When the duration of a test run reaches its time-out value, the test run is aborted, even if some tests have not been run.

When the duration of an individual test reaches its time-out value, the execution of that test stops, and the test is marked as Timeout. The test run continues with the subsequent test.

For detailed information, see: http://msdn.microsoft.com/en-us/library/ms243175.aspx.

In addition, if you could get your load test result with “Completed”, you could open your load test result-> Tables-> select the “Test Details”, what is the web test “Outcome”?

If there's any concern, please feel free to let me know.

Best Regards,

---

Jack Zhai [MSFT]
MSDN Community Support | Feedback to us

Answer 3

Hi Jack Zhai,

Thanks for helping me. I will explain the whole thing in detail.

First of all just forget load testing. I am simply running my application and a particular module gets loaded say in 8 seconds.

Now I just put a delay at the server side for 60 seconds and when i run  my application again, the server shows a "Server didnot

respond in a timely manner". What i understood from this is If the module takes more than 60 seconds to load then a timeout exception

will occur. Now i removed the code written for delaying the process and started Load testing for 250 users and 250 iterations.

In load testing I am not changing any settings for Test Timeouts in Local.testsettings. "Mark an individual test as failed if its execution time

exceeds" is kept as 30 minutes only.

The Web test results are as follows

There are around 7 urls recorded and the results for Request time  are:  0.036s,0.438s,1.287s,1.914s,1.016s,0.932s,0.632s

The  summary Load test results are:

Avg Page time is 111 seconds

Avg Response time is 78 seconds. (This is the result of a new load test i done, In the previous post it was 64 seconds.)

In the PageResults part of summary page the Avg Page time for the 7 urls  is as follows:156s,154s,127s,102s,99.6s,89.9s,49.0s

There are no test failures reported. My question is why time out is not occuring as Avg Page time is 111s? When i put a delay for 60s

in my code and run the application, the application itself is showing time outs. What is happening in this case for load  testing?

Is it like in the settings since  it is kept as 30 minutes the test won't show any failures? From the results itself time outs are expected

as Average page time is 111s. I am confused. Please help me.

 

          

           

Answer 4

Hi PhilipMG,

Sorry for my delay.

To make this issue more clearly, would you mind sharing us the screen shots?

 You put a delay at the server side for 60 seconds.

1. Then run your web test, what is your web test’s result?
2. Add this web test to the load test, and then run this load test, what is your load test’s result?
3. Please share us a screen shot like the following screen shot.

Have a nice day,

---

Jack Zhai [MSFT]
MSDN Community Support | Feedback to us

Answer 5

Hi PhilipMG,

I am writing to check the status of the issue on your side. 

What about this problem now?

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

Best Regards,

---

Jack Zhai [MSFT]
MSDN Community Support | Feedback to us

Answer 6

Hi Jack Zhai,

Sorry for the delay in responding.

Actually I found out a way of why these timeouts are not firing. In the recorded Urls of a WebPerfomancetest if we are taking the property of

each url there is a Timeout(seconds) property which is by default set to 300s. I changed this value to 180 seconds and performed the load test.

The  Timeouts are firing for those requests which take more than 180s. I did  quite a number of tests by changing the Timeout values and results 

are quite satisfactory. I also read in an article that settings in Local.testsettings have no effect in loadtestings. I don't know whether this is 

correct. I would like to know your views about conducting loadtests in this manner.

Answer 7

Hi PhilipMG,

Thank you for sharing your solutions & experience here.

If we use the web request properties “timeout”, it used to test a request total time is longer than the timeout value, and we will get the following result. The web test’s result is failed.

The timeout in the local.testsettings is used to test the whole web test, if the web test total time than the timeout value, for example, I select the “Mark an individual test as failed if its execution time exceeds” and set a short time, then I run the web test, I get the result like this:

If I add the web test to the load test with the same settings “Mark an individual test as failed if its execution time exceeds”, the load test runs well with the result “Completed”. But if I run the web test with another seting in the local.testsettings “Abort a test run if its total execution time exceeds” and set a short time, the load test result is “Aborted”, and it will give us a message box “Test run exceeded the specified time out of XX seconds”.

So as my understanding, since the load test result didn’t have the status “failed”, so I'm afraid that it didn’t support “Mark an individual test as failed if its execution time exceeds”, but it supported “Abort a test run if its total execution time exceeds” in the local.testsettings. Hope it could help.

Best Regards,

---

Jack Zhai [MSFT]
MSDN Community Support | Feedback to us

Answer 8

Hi Jack Zhai,

Thanks for  sharing your views once again. The settings in Local.testsettings donot have any effect in load testing. So I think it's better

to conduct testing by setting timeout for each request. Any way thanks... 

Answer 9

You're welcome!

Have a nice day,

---

Jack Zhai [MSFT]
MSDN Community Support | Feedback to us