0

Lets say I ran a LR script consists of usual web http/html protocol with the browser agent of Internet Explorer 8(IE8) using LR 11. The script were created using same LR version but with IE11. Kindly provide information whether this change in browser version affects anything & how exactly.

Also, please tell what happens for similar case if the record is done using LR12- IE11 & replay using LR11 - IE8.

Swarup
  • 13
  • 4

1 Answers1

0

If the server does not generate dynamic pages based upon browser type and version, then nothing from a server perspective. You may need to alter your number of download threads to accurately model a given browser however.

This thread should add some insight on the connections front

Load testing tools and concurrent connections per server browser simulation

Community
  • 1
  • 1
James Pulley
  • 5,606
  • 1
  • 14
  • 14
  • Thanks James, the thread does provide some key aspects. However, from an another angle, does this change in browser affects anyway the compatibility? I mean if the site itself is designed to be compatible with upgraded IE, by creating/running LR script in lower version affects much? – Swarup May 02 '16 at 05:55
  • @Swarup As long as the application responds to the particular script, there shouldn't be any cause for concern. Even if the site itself is designed to render appropriately only with a particular version of IE, as long as your response is as expected, load testing can continue without any issues. However, when you create scripts with a lower version of IE, you need to ensure that all the requests are appropriately captured. In the case of higher versions, there are no issues while recording or replaying. – M Navneet Krishna May 30 '16 at 09:47
  • Changing the user agent to a lower IE level could have issues on page level generation. Some of the older IE browsers required HTML constructs which were slightly off compared to standard HTML, so you may have either no browser agent condition on page generation and it produces pure HTML, or it may respond simply with a generated page of "browser not supported...." – James Pulley May 30 '16 at 23:45