Jump to content


Photo

WAPT and Browser Session


  • Please log in to reply
3 replies to this topic

#1 wiproabdn

wiproabdn

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 25 July 2013 - 02:50 PM

We are having an unexpected problem using WAPT 7.5 on an clients application. We had a number of tests which ran OK on a previous version but the application was upgraded to prevent users having the application open in two tabs at once (same user same session in IE). It now returns a message if it thinks requests are coming form different tabs in a browser.

I can still record everything OK as the application can be used as normal manually. However on script play back it fails immediately as the application appears to think successive HHTP requests from a single WAPT user violate this rule.

Has anyone encountered anything similar. I can find no way to get round this

#2 Sergei Leonov

Sergei Leonov

    Advanced Member

  • Administrators
  • PipPipPip
  • 662 posts

Posted 26 July 2013 - 05:32 AM

Usually in this case you need to parameterize your virtual user profile properly.
Sergei Leonov
WAPT Project Manager
SoftLogica LLC

Office: +7-383-335-6692
Toll-free: 1-888-364-6797 (for US only)
Time zone GMT +6, EST +11
E-mail: support@loadtestingtool.com
http://www.loadtestingtool.com

#3 wiproabdn

wiproabdn

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 26 July 2013 - 07:09 AM

Usually in this case you need to parameterize your virtual user profile properly.


Hi could you explain what you mean by that please. This happens when I use one single user with only one session so as far as I can tell there is nothing to parameterise. It fails as soon as it logs on to the system as logging on invokes three HTTP communications from the one and only session.

#4 wiproabdn

wiproabdn

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 26 July 2013 - 11:04 AM

Hi Sergei

You were right, they had implemented a thing called granitesessionid to identify source of HTTP request.
This did not exists in the previous buiId and I had completely overlooked that this was coming back with a different value on logon to the main page and required parameterisation.

Thanks for your help, your response prompted me to think in the right direction.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users