Running a test suite on alt browser

[TheaTo]

Hey all afternoon:

I'm currently on a trial version of eValid.

I'd like to know:

How do I get my test suite readied to run on an alternative browser?

Thanks

[eValid]

Hey all afternoon:

I'm currently on a trial version of eValid.

I'd like to know:

How do I get my test suite readied to run on an alternative browser?

Thanks

Hi TheoTo. Thanks for posting your question.

If you are familiar with eV.Manager you'll recognize that there is, in eV.Manger's *.ats (automated test script) file, the capability of adding switches to the system invocation of eValid that is done for each test.

All you need to do what you want is to have a separate copy of your test suite, with the addition of instances of the "-AGENT user-agent-string" in the *.ats file.

You might, for example, do this for several different browsers.

The only caveat is that if you have tests in your suite that depend graphically on the specific rendering of an item then those tests will probably FAIL if you switch the browser context from the native one (which is the IE browser) and some other browser. This is because the rendering engine on other browser, e.g. Chrome or FireFox, may differ.

Otherwise, functionally, this should work perfectly.

--eValid Support

[eValid]

Hope you are getting some good "mileage" with eValid.

Here are some other tidbits on the question you posted:

Beginning with a minimal understanding of eVManager based on the details found in our quick start webpage at:

http://www.e-valid.com/Products/Documen ... start.html

You can create a simple variant like the attached .evm and .evs examples... Please create a folder called "Project" then a sub-folder called "Group", and place browser.evm inside the Project folder.

Being that the .ats when under .evm control is strictly C program language based, we will need to either consider using separate .evs file(s) which apply
the "SetUserAgent" and/or "EnvironmentVariableFile" alternative features, etc. as the selected user agent string become more complex.

For example, Chrome uses a very long string:

"Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1667.0 Safari/537.36"

Which will not be recognized in the .ats, too many control characters..., so simply -AGENT chrome is an unknown translation/assignment...

--eValid Support