Hi,
We are evaluating Telerik Test Studio for performing functional and load tests on ASP.NET sites. So far there are some major issues that we are facing and prevent us from implementing a basic test for load test (functional test runs more or less fine). Problems are as follows:
1. There is an application server with its own authentication logic. Upon authentication user gets session identifier, which is eventually set in cookie. The problem here is that after recording a load test and re-running it, old session identifier is used. And no cookies are presented in dynamic targets so that this could somehow be fixed. In the end result application server reports back that the given session is expired and test fails.
2. On the side of ASP.NET pages are using custom PageStatePersister, which stores view state in session. And the problem here is that the data that was once stored in session page state, is discarded by other requests initiated by Test Studio. I can vaguely imagine why this is so.
To make a decision on whether to continue with Telerik Test Studio, we need to know if this is a know issue/limitation or this is something that we do wrong.
Web site and test solution are attached.
We are evaluating Telerik Test Studio for performing functional and load tests on ASP.NET sites. So far there are some major issues that we are facing and prevent us from implementing a basic test for load test (functional test runs more or less fine). Problems are as follows:
1. There is an application server with its own authentication logic. Upon authentication user gets session identifier, which is eventually set in cookie. The problem here is that after recording a load test and re-running it, old session identifier is used. And no cookies are presented in dynamic targets so that this could somehow be fixed. In the end result application server reports back that the given session is expired and test fails.
2. On the side of ASP.NET pages are using custom PageStatePersister, which stores view state in session. And the problem here is that the data that was once stored in session page state, is discarded by other requests initiated by Test Studio. I can vaguely imagine why this is so.
To make a decision on whether to continue with Telerik Test Studio, we need to know if this is a know issue/limitation or this is something that we do wrong.
Web site and test solution are attached.
2 Answers, 1 is accepted
0
Vladimir
Top achievements
Rank 1
Rank 1
answered on 17 Jun 2015, 12:56 PM
PS The test Web site has PageStatePersister alternatively using Application instead of Session. But this is not an option for our application. And generally it is not the best idea.
0
Hi Vladimir,
I see what the problem is. You're using an AJAX update panel to update the hidden __PAGESTATEKEY input field - see attached screen shot. Test Studio load test cannot parse the contents of update panel responses in order to update the value of __PAGESTATEKEY for the next request. As a result all you will get is the original recorded value sent back to the web server.
You need to pull __PAGESTATEKEY out of the update panel and have it updated via full HTML page responses for it to be compatible with a Test Studio load test.
Regards,
Cody
Telerik
I see what the problem is. You're using an AJAX update panel to update the hidden __PAGESTATEKEY input field - see attached screen shot. Test Studio load test cannot parse the contents of update panel responses in order to update the value of __PAGESTATEKEY for the next request. As a result all you will get is the original recorded value sent back to the web server.
You need to pull __PAGESTATEKEY out of the update panel and have it updated via full HTML page responses for it to be compatible with a Test Studio load test.
Regards,
Cody
Telerik