I understand, but as a performance test professional it is your
obligation and responsibility to educate your clients on what is a
performance requirements (server facing) and what is a functional
requirement (client facing). If you can demonstrate via server logs
(Agent String) that the server believes it has been hit by all of your
different browser types then will the requirement for the mix of browser
types be satisfied. (Just for kicks include an agent string for (IE 10,
Engineering Alpha, .Net 5.00001 Alpha, Do not release in the wild!) and
see if anyone notices.
Barring the cultural divide on IE rendering vs everyone else, the HTML
sent to your client is going to fall into two camps, IE and non-IE.
You can exercise both by changing the agent string. And you only need
to do this if your application specifically calls out differences in
HTML for rendering for IE. Speak to your developers about this, they
should know if they are handling IE generated HTML any differently.
The entire rest of the universe gets the same non-IE HTML in that case.
Next questions: OK, so you have found that Opera and Chrome have a
deviation in performance vs Firefox, IE and the AOL browser version 1.
Since you don't own the source code for opera or chrome what then is
your reconciliation method? How are you going to tune code you don't
have access to for rendering purposes? How will you mandate that your
end clients update to this code and they haven't installed 60 tool bars
which are slowing the browser to a crawl?
James Pulley
=============================================================
Off Site, On Shore LoadRunner Services beginning at 19.95 USD
http://www.loadrunnerbythehour.com
=============================================================