My aim is to write a test case which should be working for different type of device
Usecase: Launch the application main, and search for an application, click and launch it instead of using the package and activity
But the challenge is it should work across all devices, because some device scroll up and down to access the next screen of app try, some device scroll right left
How can this be handled, please advice
If you need to access native android features, I fear you will need to create a database of devices and record their behavior. Two alternatives that i can think of are (a) copy the app to the home page so you don’t have to navigate through the application list, and (b) launch the app using the package name. The latter one has appium support (or you can write your own simple adb module if you are never going to use service such as TestDroid), but won’t satisfy your requirements if you need to test that you can launch the app through the home page.
Hi willosser, thanks for the information, ya i know the complexity of launching the application from the menu screen…
But 1 of our test cases say that so could you give some more information about creating a database, it will be helpful
While I can’t recommend this as the best solution, here was our exhaustive approach:
We created our own adb module because appium doesn’t provide access to some information gathering commands we needed.
For each device, get the make and model. Add them to a data file and record the behavior of the application screen – does it scroll up/down or left/right. Once you’ve modeled all your devices, you are good to go, adding devices as you obtain them. If this is all you are doing, then it’s not that complex. We mapped out the behavior of all the settings screens and how to navigate to the subscreens if we couldn’t get there directly through launching the app.