--
You received this message because you are subscribed to the Google "LoadRunner" group.
To post to this group, send email to LR-Loa...@googlegroups.com
To unsubscribe from this group, send email to
LR-LoadRunne...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/LR-LoadRunner?hl=en
2. Go to your web server logs and read a couple of pieces of the log.
Then go to the options for browser emulation and select custom string.
Visualize the information presented within the log on the web server and
then change your browser to represent "windows 2015, IE20 Engineering
Alpha, do not use outside of Microsoft." Run your virtual user.
Look in the web server logs for your session information. Make sense?
The only real reason that browser version makes one whit of difference
is if your backend application rendering engine makes different choices
for rendering the HTML based upon VERSION AND TYPE of browser. I have
yet to find both of those conditions in place, instead the decision is
usually "in gross" in the topic of specific rendering for non-HTML
standard for IE and true HTML standard for non-IE. For additional
reading on this topic I recommend the reference "PHP and MYSQL for
Dummies" with particular attention paid to conditional rendering for IE.
3. The server really has no idea what browser is on the other end of
the conversation beyond how the browser and client operating system
announces itself. See announcement via custom string in 2 above.
4. Isn't this really a question you should be answering with a
functional test before you run a performance test? If it will not work
for one then it will never work for many. This question would suggest
that you may be co-mingling your functional and performance tests, which
is generally not recommended.
James Pulley, http://www.loadrunnerbythehour.com