android-uiautomator

I have done some Googling and searched in Android Developer website but I could not able to find a suitable answer. Can anyone help me out for this? thanks in advance. Key Differences: What they represent Waiting for views to exist/finding views Scrolling What they represent In my words, UiObject2 is a direct representation of a real view that exists on the screen and allows you to take actions on that view. UiObject is a representation of how to find an element that may be on the screen, combined with actions that you can take on that view. UiObject as the docs say , represents the method to

I want to automate mobile web site testing on Android emulator using c# and Appium. There is a simple test scenario I want to automate for the start: 1. Start Browser 2. Find an element 3. Clear it 4. Send keys I've got a problem with the second step. Every time MSTest tries to execute FindElementById line in the code below, I get the error: "An element could not be located on the page using the given search parameters." [TestClass] public class UnitTest1 { private DesiredCapabilities _capabilities; private AndroidDriver _driver; public void InitializeDriver() { Console.WriteLine("Connecting

I am writing a test that requires launching application directly from launcher. Because I can't emulate it correctly by launching through intent. The problem is that when I am running the test on a fresh emulator (I am using Travis CI, but it can be easily reproduced on my home PC) the emulator starts with the "first run" greeter overlay. Which blocks my uiautomator code from correctly launching the application. I have tried to add some code to close that greeter but unfortunately it can appear with some delay, when my "greeter detecting and closing" code has already stopped working thinking

I am currently testing an application that should be set as the default launcher. I already have a set of Espresso tests running, but they only work if the user has previously selected my app as the launcher. The dialog that appears to the user so that he can select the launcher is not reachable by Espresso , since it is outside the app itself. However, UIAutomator would be perfectly able to interact with it. Hence, I would like to know if it is possible to use some kind of UIAutomator script before the Espresso tests. Since UIAutomator 2.0 is now based on Android Instrumentation, you can run

I'm trying to identify the parent view of an ui element so I can navigate through the UI freely. For example, in Settings app, I can find the view with the text "Bluetooth": UiObject btView = new UiObject(new UiSelector().text("Bluetooth")); Now, the part where I get stuck is this one: I want to navigate two levels up and start a new search for the on/off button that enables and disables bluetooth. Note: I can get the button if I use the code below. UiObject btButtonView = new UiObject(new UiSelector().className("android.widget.Switch").instance(1)); This searches for switch buttons and

I've been looking for a way to test the UI of my Fragments separately (ie, independently from other fragments and activities) but I can't find a way to do it. In particular, let's say I have Fragment A, Fragment B and Fragment C. The only way (app-wise) to go to Fragment C is by passing through Fragment A and Fragment B first. I am looking for a way to test Fragment C directly (potentially by mocking its dependencies, if any exists), without having to pass through Fragment A and B. Tools I investigated so far: monkey: only used to generate pseudo-random events through command line. Not what I