Web Automation and Repositories
Posted: Wed Jun 03, 2015 2:16 pm
Hi,
We've created a bunch of website tests that run on desktops supporting Chrome, IE and Firefox. The next phase is to create the same tests for IOS & Android. I'm aware that we can only create them using the rxBrowser. What I would like to know is whether I should use the existing repository or create a new repository solely for IOS & Android? In order to use the existing I would probably need to write some user code that works out what platform the tests are running in.
Just to be clear we're not planing to automate a mobile app, but the idea is to automate web testing on devices.
Having two sets of repositories could be more of a maintenance task when the underline object recognition is more or less the same? Or is it?
Please share any thoughts or experiences or even what's best practise.
Thanks,
Sanjay
We've created a bunch of website tests that run on desktops supporting Chrome, IE and Firefox. The next phase is to create the same tests for IOS & Android. I'm aware that we can only create them using the rxBrowser. What I would like to know is whether I should use the existing repository or create a new repository solely for IOS & Android? In order to use the existing I would probably need to write some user code that works out what platform the tests are running in.
Just to be clear we're not planing to automate a mobile app, but the idea is to automate web testing on devices.
Having two sets of repositories could be more of a maintenance task when the underline object recognition is more or less the same? Or is it?
Please share any thoughts or experiences or even what's best practise.
Thanks,
Sanjay