I'm facing an issue while running a recorded test scenario of an application login using a single user on JMeter.

I've used JMeter's proxy server to record all the requests of the login scenario. The proxy server records all the requests fine. When i play the recorded scenario, the login step gives response data that contains "Your session has expired". It seems that the JSF ViewState value is getting hard-coded when I record the requests due to which when the steps are played the new ViewState values generated from the server do not match.

I tried using solutions given in these links to handle ViewState values:

• Testing a JSF Application with JMeter
• How to handle JSF viewstate with jmeter
• JMeter handling dynamic ViewState parameter in Seam framework
• How to modify JMeter scripts which handle JSF ViewState?.

But still it doesn't work.
Am i missing something?
Or is it something other than the ViewState that's causing the recorded steps to fail?

Screenshots below:

screen #1

screen #2

screen #3

I'm facing an issue while running a recorded test scenario of an application login using a single user on JMeter.

I've used JMeter's proxy server to record all the requests of the login scenario. The proxy server records all the requests fine. When i play the recorded scenario, the login step gives response data that contains "Your session has expired". It seems that the JSF ViewState value is getting hard-coded when I record the requests due to which when the steps are played the new ViewState values generated from the server do not match.

I tried using solutions given in these links to handle ViewState values:

• Testing a JSF Application with JMeter
• How to handle JSF viewstate with jmeter
• JMeter handling dynamic ViewState parameter in Seam framework
• How to modify JMeter scripts which handle JSF ViewState?.

But still it doesn't work.
Am i missing something?
Or is it something other than the ViewState that's causing the recorded steps to fail?

Screenshots below:

screen #1

screen #2

screen #3

I'm facing an issue while running a recorded test scenario of an application login using a single user on JMeter. I've used JMeter's proxy server to record all the requests of the login scenario. The proxy server records all the requests fine. When i play the recorded scenario, the login step gives response data that contains "Your session has expired". It seems that the JSF ViewState value is getting hardcoded when I record the requests due to which when the steps are played the new ViewState values generated from the server do not match. I tried using solutions given in these links to handle ViewState values:

(Link)http://wiki.apache.org/myfaces/PerformanceTestingWithJMeter

(Link)http://www.sqaforums.com/showflat.php?Number=572893

(Link)http://anahorny.blogspot.in/2011/03/jmeter-handling-dynamic-viewstate.html

(Link)http://jmeter.512774.n5.nabble.com/How-to-modify-JMeter-scripts-which-handle-JSF-ViewState-td525955.html

But still it doesn't work. Am i missing something? Or is it something other than the ViewState that's causing the recorded steps to fail?

I had uploaded screenshots for reference here but being a new user, i wasn't allowed to post images.

So, here are links to the screenshots:

(Link)http://dl.dropbox.com/u/58460235/Screenshot-login.jmx%20(-home-abhijeet-load_test_plans-login.jmx)%20-%20Apache%20JMeter%20(2.7%20r1342410)-1.png

(Link)http://dl.dropbox.com/u/58460235/Screenshot-login.jmx%20(-home-abhijeet-load_test_plans-login.jmx)%20-%20Apache%20JMeter%20(2.7%20r1342410)-2.png

(Link)http://dl.dropbox.com/u/58460235/Screenshot-login.jmx%20(-home-abhijeet-load_test_plans-login.jmx)%20-%20Apache%20JMeter%20(2.7%20r1342410).png

I'm facing an issue while running a recorded test scenario of an application login using a single user on JMeter.

I've used JMeter's proxy server to record all the requests of the login scenario. The proxy server records all the requests fine. When i play the recorded scenario, the login step gives response data that contains "Your session has expired". It seems that the JSF ViewState value is getting hard-coded when I record the requests due to which when the steps are played the new ViewState values generated from the server do not match.

I tried using solutions given in these links to handle ViewState values:

• Testing a JSF Application with JMeter
• How to handle JSF viewstate with jmeter
• JMeter handling dynamic ViewState parameter in Seam framework
• How to modify JMeter scripts which handle JSF ViewState?.

But still it doesn't work.
Am i missing something?
Or is it something other than the ViewState that's causing the recorded steps to fail?

Screenshots below:

screen #1

screen #2

screen #3