Java-client 2.1.0 released

[JohnBinish]

Thanks @SergeyTichomirov. I may have to create separate classes to handle different drivers. to give an backgroud about where I am facing issues: I am trying to create a tool agnostic keyword driven framework for mobile testing tools.For example Keywords like set to ‘set’ to set the text.These will work in Appium,Calabash and other tools also Web,Hybrid and Native for Android and iOS

[SergeyTichomirov]

@JohnBinish

I may have to create separate classes to handle different drivers. to give an backgroud about where I am facing issues

Is it all about statistics?

[jonahss]

Is StartActivity still not working? Didn’t make any changes, but maybe broke something by mistake.

[Arvind_Patel]

its working , that was my fault

[Mayuresh_Shirodkar]

On adding java client 2.1.0 to java build path, I am unable to get the below methods.
findElementByIosUIAutomation()
findElementsByIosUIAutomation()
findElementByAndroidUIAutomator()
findElementsByAndroidUIAutomator()

[SergeyTichomirov]

These methods are not implemented by AppiumDriver now. They are implemented by AndroidDriver and IOSDriver.

You can use

driver.findElement(MobileBy.IosUIAutomation(“yourlocator”))

instead of them.

[Mayuresh_Shirodkar]

Yup got it :)…Thanks for the reply…

[Sandipan_Jana]

Hi,
I am new to appium. Currently I am using scrollTo and scrollExact method for android emulator. Both are scrolling but it is scrolling till the end.But I wnt it to scroll to specific element.
Can anyone help me on that or whether that is a bug?
I am using java-client-2.1.0.jar

[Appium_Master]

Hi @Sandipan_Jana ,
You can check my comments and video on below link

How the scrollTo() and scrollToExact() methods are working?

I’m trying to figure out how the two methods are working, since it doesn’t scroll the screen. I’m using the scrolling method like that: driver.scrollTo("Register"); //where "Register" is the text displayed on the button Should it work like that? What if I want to scroll to an element and find it By its Id?

[noviceappium]

HI, I Tried to perform a swipe with this method. I don’t have error message in Appium but it doesn’t work.

I use this code to initialize the driver:

    import io.appium.java_client.AppiumDriver;

    import io.appium.java_client.ios.IOSDriver;
    import org.apache.commons.io.FileUtils;
    import org.openqa.selenium.OutputType;
    import org.openqa.selenium.WebDriver; 
    import org.openqa.selenium.remote.Augmenter; 
    import org.openqa.selenium.remote.DesiredCapabilities; 
    import java.io.File; 

public class Application {

            private final static String APPIUM_PORT = "4723";
             private final static String APPIUM_HOST = "127.0.0.1";
             public static AppiumDriver driver;     
		         capabilities.setCapability("platformName", "iOS"); 
            … 
            setDriver(new IOSDriver(new URL("http://" + appiumHost + ":" + appiumPort + "/wd/hub"), capabilities));
}

… and this code to perform the swipe:

public static void testSwipe(){
MobileElement element = (MobileElement) driver.findElement(By.xpath(“//UIAApplication[1]/UIAWindow[1]/UIAScrollView[1]/UIAStaticText[2]”));
element.click(); // OK
element.swipe(SwipeElementDirection.LEFT, 1000); // Test Swipe #1 : KO
driver.swipe(300, 400, 10, 400, 500); // Test Swipe #2 : KO
}

[okiichinpo]

I am trying to use this new method with IOS automation and it is working but it is slow what is the second parameter 1000 do?

[awang]

Hi @okiichinpo,

I’m guessing you’re talking about the first post in this thread. I believe the 1000 refers to the duration of the command in milliseconds.

[okiichinpo]

@awang So does that mean it will swipe for that long? What I am trying to do is find an element that is not on the screen.

[okiichinpo]

@awang Thanks for responding btw

[awang]

@okiichinpo, yes, I believe that is what it means. The swipe will occur over a time interval of 1000 milliseconds.

For finding elements that are not on screen: I know that sometimes the element isn’t returned by Instruments. I am guessing it’s because the element hasn’t been prepared in the device or simulator memory, so you have to swipe the screen until the element is close enough to the viewable area of the screen that the element gets instantiated.

[mamathas]

Hi,

I tried to use swipe(direction, int) on a MobileElement.

But, I am not able to tune the duration so that the element is swiped to left instead of simulating a click on that element. If I set it to 500, it simply tries to swipe but not enough duration to reveal underlying options. If I keep increasing the duration upto 1000, it starts to click on that element and opens a new view.

Please help me.

Thanks,
Mamatha

[shilpi]

scrollTo not working. i am using java client 2.1.0. jar file.

[Brian_Watson]

Since this is a 2 year old thread about a two year old version of the client, I think you’d be best off trying a little newer version of the client. Try java-client 4.1.2 if you are still running Appium server 1.5.3. That one has been out a while and is pretty stable.

Otherwise, you could also try upgrading to Appium 1.6.4-beta server, along with the java-client 5.0.0-BETA4

[shilpi]

i am using appium 1.6.4also used java client 5.0.0 still it’s not working. not able to click on a particular element. scrollToexact() also not working.

[Venkatesh]

Scroll to Exact works but you need to provide additional timeout while starting appium server. I have noticed command timing out with Appium Server default timeout.