Answered question

Assertion Failed on Viewstate validation

I have verified that my Viewstate and Eventvalidation parameters are being extracted correctly as variables. I'm running into the issue where my users are being redirected from a Terms and Conditions page and the viewstate doesn't generate anymore but rather redirects. I believe it's because the test is reusing some of my users and once they have accepted terms and conditions, they do not see that page anymore and are redirected to the next page. What I can't figure out is, why is my test run reusing some of my users? I'm pretty sure I've used every combination in the value change policy and distribution policy. Attached is what I currently have configured.

Kevin S.
Kevin S.

Kevin S.

Level
0
25 / 100
points
Fousseyni B.
Fousseyni B.

Fousseyni B.

Level
1
351 / 750
points

Hello Kevin,

Did you delete the used row before checking your user path between every check ? In fact, Neoload does not delete any row after using it in a file variable.
You can set up the change policy to "on each iteration". Before doing that, clean up the used row in the file you are using as a file variable.

Best Regards,
Fousseyni B.

Did you find this useful ?

No (0)

Yes (1)

100%

100% of users found this answer useful

Other answers

Fousseyni B.
Fousseyni B.

Fousseyni B.

Level
1
351 / 750
points

Hello Kevin S,

Did you try to set up the scope value of the variable values distribution policy to "Unique" ?

Best regards,
Fousseyni B.

Neil W.
Neil W.

Neil W.

Level
3
2057 / 5000
points
Team

Looking at your screen shot, you are stopping the test once all the data is used so I don't see how you can be reusing the same user details. Are you sure your assumption is correct?

Kevin S.
Kevin S.

Kevin S.

Level
0
25 / 100
points

Fousseyni, Yes I have tried to set it to Unique and get the same results.
Neil, I agree, I don't understand how that's happening. I do know I'm able to get the same exact assertion fails when I check the user path twice in a row!

Kevin S.
Kevin S.

Kevin S.

Level
0
25 / 100
points

Thanks Fousseyni, I think setting the change policy to "on each iteration has made a difference and I'm no longer seeing those errors. I tried that before and it didn't work, so it might be a combination of that and another change I made. but thank you!