Agree with Krishnan, Marimuthu's approach can set user agent string,
faking the browser to the website/server, but it will of course
actually be using the wrong browser/WebDriver. It would be same as
using HTTP request libraries and setting HTTP request header
specifying user agent string to the website/server.
But this also brings back my original question, why even bother
setting user agent string for a mobile browser? Unless you are testing
from desktop and faking as mobile browser. Or unless you want to test
unsupported mobile browser by faking as it (e.g. Opera Mobile/Mini vs
WebDriver's iPhone/iPad driver which is for mobile Safari).
On Feb 15, 3:14 am, Krishnan Mahadevan