TestMu 2025 - The Largest Virtual Software Testing Conference is Back | 50,000+ Attendees

How to use doubleTap method of org.openqa.selenium.interactions.Interface TouchScreen class

Best Selenium code snippet using org.openqa.selenium.interactions.Interface TouchScreen.doubleTap

...45	 * @throws IllegalStateException46	 *           if there are no last active coordinates and {@code where} is47	 *           {@code null}48	 */49	void doubleTap(@Nullable Coordinates where);50	/**51	 * Issues a touch down event at the given coordinates.52	 * 53	 * @param where54	 *          coordinates where the touch down event is issued. If {@code null},55	 *          the touch down event is issued at the last active coordinates.56	 * 57	 * @throws IllegalStateException58	 *           if there are no last active coordinates and {@code where} is59	 *           {@code null}60	 */61	void touchDown(@Nullable Coordinates where);62	/**63	 * Issues a touch up event at the given coordinates....

Source: TouchActions.java

...28		//Get Coordinate for element29		Coordinates Ele_co=((Locatable)Element).getCoordinates();30		31		32		touch.doubleTap(Ele_co);33		touch.singleTap(Ele_co);34		touch.longPress(Ele_co);35		36		37		/*38		 * Tocuh action39		 * https://seleniumhq.github.io/selenium/docs/api/java/org/openqa/selenium/interactions/touch/TouchActions.html40		 */41		42		43		44	}4546}
...

Source: TouchScreen.java

...11  public abstract void move(int paramInt1, int paramInt2);12  13  public abstract void scroll(Coordinates paramCoordinates, int paramInt1, int paramInt2);14  15  public abstract void doubleTap(Coordinates paramCoordinates);16  17  public abstract void longPress(Coordinates paramCoordinates);18  19  public abstract void scroll(int paramInt1, int paramInt2);20  21  public abstract void flick(int paramInt1, int paramInt2);22  23  public abstract void flick(Coordinates paramCoordinates, int paramInt1, int paramInt2, int paramInt3);24}...

doubleTap

Using AI Code Generation

1TouchScreen touchScreen = ((HasTouchScreen)driver).getTouch();2DoubleTapAction doubleTap = new DoubleTapAction(touchScreen);3doubleTap.perform();4TouchScreen touchScreen = ((HasTouchScreen)driver).getTouch();5DoubleTapAction doubleTap = new DoubleTapAction(touchScreen);6doubleTap.perform();7TouchScreen touchScreen = ((HasTouchScreen)driver).getTouch();8DoubleTapAction doubleTap = new DoubleTapAction(touchScreen);9doubleTap.perform();10TouchScreen touchScreen = ((HasTouchScreen)driver).getTouch();11DoubleTapAction doubleTap = new DoubleTapAction(touchScreen);12doubleTap.perform();13TouchScreen touchScreen = ((HasTouchScreen)driver).getTouch();14DoubleTapAction doubleTap = new DoubleTapAction(touchScreen);15doubleTap.perform();16TouchScreen touchScreen = ((HasTouchScreen)driver).getTouch();17DoubleTapAction doubleTap = new DoubleTapAction(touchScreen);18doubleTap.perform();19TouchScreen touchScreen = ((HasTouchScreen)driver).getTouch();20DoubleTapAction doubleTap = new DoubleTapAction(touchScreen);

doubleTap

Using AI Code Generation

1import org.openqa.selenium.WebDriver;2import org.openqa.selenium.WebElement;3import org.openqa.selenium.interactions.Actions;4import org.openqa.selenium.interactions.Interface TouchScreen;5import org.openqa.selenium.interactions.Sequence;6import org.openqa.selenium.support.FindBy;7import org.openqa.selenium.support.PageFactory;8import org.openqa.selenium.support.ui.WebDriverWait;9import org.testng.annotations.BeforeClass;10import org.testng.annotations.Test;11import static org.testng.Assert.assertEquals;12public class DoubleTapTest {13    private WebDriver driver;14    private WebDriverWait wait;15    private Interface TouchScreen touch;16    private Actions builder;17    private Sequence sequence;18    @FindBy(id = "doubleTap")19    private WebElement doubleTap;20    public void setUp() {21        driver = new FirefoxDriver();22        wait = new WebDriverWait(driver, 10);23        builder = new Actions(driver);24        touch = (Interface TouchScreen) builder;25        PageFactory.initElements(driver, this);26    }27    public void testDoubleTap() {28        sequence = new Sequence(builder);29        sequence.addAction(touch.down(doubleTap).waitAction(1000).up(doubleTap));30        sequence.addAction(touch.down(doubleTap).waitAction(1000).up(doubleTap));31        touch.perform(sequence);32        assertEquals(driver.switchTo().alert().getText(), "Double Tap!");33        driver.switchTo().alert().accept();34    }35    public void tearDown() {36        driver.quit();37    }38}

doubleTap

Using AI Code Generation

1import org.openqa.selenium.interactions.Interface TouchScreen;2import org.openqa.selenium.interactions.touch.TouchActions;3import org.openqa.selenium.interactions.touch.DoubleTapAction;4import org.openqa.selenium.interactions.touch.DownAction;5import org.openqa.selenium.interactions.touch.UpAction;6import org.openqa.selenium.interactions.touch.MoveAction;7Interface TouchScreen touch = ((Interface TouchScreen) driver);8TouchActions action = new TouchActions(touch);9DoubleTapAction doubleTap = new DoubleTapAction(touch);10action.down(100,100).move(200,200).up(200,200).doubleTap(300,300).perform();11import java.net.URL;12import org.openqa.selenium.remote.DesiredCapabilities;13import org.openqa.selenium.interactions.Interface TouchScreen;14import org.openqa.selenium.interactions.touch.TouchActions;15import org.openqa.selenium.interactions.touch.DoubleTapAction;16import org.openqa.selenium.interactions.touch.DownAction;17import org.openqa.selenium.interactions.touch.UpAction;18import org.openqa.selenium.interactions.touch.MoveAction;19import io.appium.java_client.android.AndroidDriver;20import io.appium.java_client.android.AndroidElement;21import io.appium.java_client.remote.MobileCapabilityType;22public class DoubleTap {23public static void main(String[] args) throws InterruptedException {24DesiredCapabilities cap = new DesiredCapabilities();25cap.setCapability(MobileCapabilityType.DEVICE_NAME, "Android Device");26cap.setCapability(MobileCapabilityType.PLATFORM_NAME, "Android");27cap.setCapability(MobileCapabilityType.PLATFORM_VERSION, "7.0");28cap.setCapability("appPackage", "com.google.android.apps.messaging");29cap.setCapability("appActivity", "com.google.android.apps.messaging.ui.ConversationListActivity");

doubleTap

Using AI Code Generation

1import org.openqa.selenium.By;2import org.openqa.selenium.WebDriver;3import org.openqa.selenium.WebElement;4import org.openqa.selenium.chrome.ChromeDriver;5import org.openqa.selenium.interactions.Action;6import org.openqa.selenium.interactions.Actions;7import org.openqa.selenium.interactions.InterfaceTouchScreen;8import org.openqa.selenium.interactions.TouchScreen;9import org.openqa.selenium.support.ui.ExpectedConditions;10import org.openqa.selenium.support.ui.WebDriverWait;11public class DoubleClick {12    public static void main(String[] args) {13        System.setProperty("webdriver.chrome.driver",14                "/Users/ahmetorhan/Documents/selenium dependencies/drivers/chromedriver");15        WebDriver driver = new ChromeDriver();16        driver.manage().window().maximize();17        WebDriverWait wait = new WebDriverWait(driver, 10);18        Actions builder = new Actions(driver);19                .moveToElement(element)20                .doubleClick()21                .build();22        seriesOfActions.perform();23        TouchScreen touchScreen = ((InterfaceTouchScreen) driver).getTouch();24        touchScreen.doubleTap(element);25    }26}

StackOverFlow community discussions

Questions

Discussion

What is difference between Implicit wait and Explicit wait in Selenium WebDriver?

Should we write separate page-object for pop-up with a selection drop-down?

Selecting Nth-of-type in selenium

Capturing browser logs with Selenium WebDriver using Java

Call a Class From another class

Selenium Web Driver : Handle Confirm Box using Java

How to explicitly wait while using page factory in Selenium?

org.openqa.selenium.WebDriverException: unknown error: cannot determine loading status

Check if element is clickable in Selenium Java

Kill chromedriver process in Selenium / Java

Check the below links:

Implicit Wait - It instructs the web driver to wait for some time by poll the DOM. Once you declared implicit wait it will be available for the entire life of web driver instance. By default the value will be 0. If you set a longer default, then the behavior will poll the DOM on a periodic basis depending on the browser/driver implementation.
Explicit Wait + ExpectedConditions - It is the custom one. It will be used if we want the execution to wait for some time until some condition achieved.

https://stackoverflow.com/questions/22656615/what-is-difference-between-implicit-wait-and-explicit-wait-in-selenium-webdriver

I'm not enirely sure which one you want to select, but you should play around more with the :nth-* pseudo-classes. Here is a CSS selector that selects all 3 c3's using nth-child()

div.c1 div.c3:nth-child(1)

Like i said, you haven't really specified which one you want to select.

but my lack of understanding on nth-of-type is driving me crazy. Can anyone offer insight to why the second 2 don't work or correct my basic lack of comprehension on this selector?

One thing to keep in mind, is all of the :nth-*() pseudo-classes are dependent on their parents. Let me translate your selector:

.c1:nth-of-type(2)

Find anything with a class of c1 that is a second child.

In your case, <body> was most likely the parent, so...

<body>
  <div .c1 />
  <div .c1 /> // it highlights this one, because it's the 2nd child of the type ".c1"
  <div .c1 />
</body>

Now let me explain why your other selectors are not working.

Both .c2:nth-of-type(2) and .c3:nth-of-type(2) are looking at the parent's as well. since you are specifying a parent, it's expecting <body> as the parent. In your case, <body> isn't the parent.. the <div .c1 /> is. In reality, that selector is looking for the DOM -

<body>
  <div .c1 />
  <div .c2 /> // this **would** be the second nth-of-type, but it's not really this way. 
  <div .c1 />
</body>

Play around with the different css selectors and pseudo-classes at http://cssdesk.com it's very helpful to actively experiment on your own. you'll figure it out.

https://stackoverflow.com/questions/19909458/selecting-nth-of-type-in-selenium

I assume it is something in the lines of:

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.logging.LogEntries;
import org.openqa.selenium.logging.LogEntry;
import org.openqa.selenium.logging.LogType;
import org.openqa.selenium.logging.LoggingPreferences;
import org.openqa.selenium.remote.CapabilityType;
import org.openqa.selenium.remote.DesiredCapabilities;
import org.testng.annotations.AfterMethod;
import org.testng.annotations.BeforeMethod;
import org.testng.annotations.Test;

public class ChromeConsoleLogging {
    private WebDriver driver;


    @BeforeMethod
    public void setUp() {
        System.setProperty("webdriver.chrome.driver", "c:\\path\\to\\chromedriver.exe");        
        DesiredCapabilities caps = DesiredCapabilities.chrome();
        LoggingPreferences logPrefs = new LoggingPreferences();
        logPrefs.enable(LogType.BROWSER, Level.ALL);
        caps.setCapability(CapabilityType.LOGGING_PREFS, logPrefs);
        driver = new ChromeDriver(caps);
    }

    @AfterMethod
    public void tearDown() {
        driver.quit();
    }

    public void analyzeLog() {
        LogEntries logEntries = driver.manage().logs().get(LogType.BROWSER);
        for (LogEntry entry : logEntries) {
            System.out.println(new Date(entry.getTimestamp()) + " " + entry.getLevel() + " " + entry.getMessage());
            //do something useful with the data
        }
    }

    @Test
    public void testMethod() {
        driver.get("http://mypage.com");
        //do something on page
        analyzeLog();
    }
}

Source : Get chrome's console log

https://stackoverflow.com/questions/25431380/capturing-browser-logs-with-selenium-webdriver-using-java

Suposse you have

Class1

public class Class1 {
    //Your class code above
}

Class2

public class Class2 {
}

and then you can use Class2 in different ways.

Class Field

public class Class1{
    private Class2 class2 = new Class2();
}

Method field

public class Class1 {
    public void loginAs(String username, String password)
    {
         Class2 class2 = new Class2();
         class2.invokeSomeMethod();
         //your actual code
    }
}

Static methods from Class2 Imagine this is your class2.

public class Class2 {
     public static void doSomething(){
     }
}

from class1 you can use doSomething from Class2 whenever you want

public class Class1 {
    public void loginAs(String username, String password)
    {
         Class2.doSomething();
         //your actual code
    }
}

https://stackoverflow.com/questions/19809739/call-a-class-from-another-class

different dialogs handling using selenium webDriver:

import org.openqa.selenium.Alert;
import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.firefox.FirefoxDriver;

public class JavaScriptAlertTest {

public static void main(String[] args) {

    WebDriver myTestDriver = new FirefoxDriver();
    myTestDriver.get("...blablabla....");

    myTestDriver.manage().window().maximize();

    myTestDriver.findElement(By.xpath("//input[@value = 'alert']")).click();

    Alert javascriptAlert = myTestDriver.switchTo().alert();
    System.out.println(javascriptAlert.getText()); // Get text on alert box
    javascriptAlert.accept();

    System.out.println("*************prompt******************************************");

    myTestDriver.findElement(By.xpath("//input[@value = 'prompt']")).click();

    Alert javascriptprompt = myTestDriver.switchTo().alert();
    javascriptprompt.sendKeys("This is Selenium Training");

    System.out.println(javascriptprompt.getText()); // Get text on alert box

    javascriptprompt.accept();
    javascriptprompt = myTestDriver.switchTo().alert();

    System.out.println(javascriptprompt.getText()); // Get text on alert box
    javascriptprompt.accept();

    myTestDriver.findElement(By.xpath("//input[@value = 'prompt']")).click();

    javascriptprompt = myTestDriver.switchTo().alert();

    System.out.println(javascriptprompt.getText()); // Get text on alert box

    javascriptprompt.dismiss();
    javascriptprompt = myTestDriver.switchTo().alert();

    System.out.println(javascriptprompt.getText()); // Get text on alert box
    javascriptprompt.accept();

    System.out.println("***********************************confirm dialog box****************************");
    myTestDriver.findElement(By.xpath("//input[@value = 'confirm']")).click();

    Alert javascriptconfirm = myTestDriver.switchTo().alert();
    javascriptconfirm.accept();

    javascriptconfirm = myTestDriver.switchTo().alert();
    System.out.println(javascriptconfirm.getText()); // Get text on alert box
    javascriptconfirm.accept();

    myTestDriver.findElement(By.xpath("//input[@value = 'confirm']")).click();
    javascriptconfirm = myTestDriver.switchTo().alert();

    javascriptconfirm.dismiss();
    javascriptconfirm = myTestDriver.switchTo().alert();
    System.out.println(javascriptconfirm.getText()); // Get text on alert box
    javascriptconfirm.accept();

}
}

Hope it helps you:)

https://stackoverflow.com/questions/13560120/selenium-web-driver-handle-confirm-box-using-java

I would suggest that you use the PageFactory as intended and have a constructor for your class where you would like to use the explicit wait. Having a separation between the script and the page objects makes it much easier to work with in the future.

public class MyClass {

    WebDriverWait wait; 
    WebDriver driver; 
    @FindBy(how=How.ID, id="locatorId")
    WebElement locator; 

    // Construct your class here 
    public MyClass(WebDriver driver){
        this.driver = driver; 
        wait = new WebDriverWait(driver,30);
    }

    // Call whatever function you want to create 
    public void MyFunction(){
        wait.until(ExpectedConditions.presenceOfElementLocated(locator));
        // Perform desired actions that you wanted to do in myClass
    }

Then in your test case use code to perform your test. In your example, the wait is contained inside the page.

public class MyTestClass {
    public static void main (string ... args){
        WebDriver driver = new FireFoxDriver(); 
        MyClass myForm = PageFactory.initElements(driver,Myclass.class); 
        myForm.MyFunction(); 
    }
}

This example was modeled after the example in the book Selenium WebDriver Practical Guide that can be found here here

https://stackoverflow.com/questions/47191185/how-to-explicitly-wait-while-using-page-factory-in-selenium

The error says it all :

org.openqa.selenium.WebDriverException: unknown error: cannot determine loading status
from unknown error: missing or invalid 'entry.level'

Your main issue is the version compatibility among the binaries you are using as follows :

You are using chromedriver=2.29.461591
Release Notes of chromedriver=2.29.461591 clearly mentions the following :

Supports Chrome v56-58

You are using chrome=63.x
Release Notes of ChromeDriver v2.34 clearly mentions the following :

Supports Chrome v61-63

Release Notes of ChromeDriver v2.35 clearly mentions the following :

Supports Chrome v62-64

You are using Selenium Version 3.5.3.
Your JDK version is 1.8.0_131.

So there is a clear mismatch between the chromedriver version (v2.29.4) [which supports Chrome v56-58] with the Chrome Browser version (v63.x) [supported by ChromeDriver v2.34 minimum]

Solution

Upgrade JDK to recent levels JDK Version 8 Update 151.
Upgrade Selenium to current levels Version 3.8.1.
Upgrade ChromeDriver to ChromeDriver v2.35 level.
Keep Chrome to Chrome v64.x levels. (as per ChromeDriver v2.35 release notes)
Execute your Test.

https://stackoverflow.com/questions/48473618/org-openqa-selenium-webdriverexception-unknown-error-cannot-determine-loading

elementToBeClickable is used for checking an element is visible and enabled such that you can click it.

ExpectedConditions.elementToBeClickable returns WebElement if expected condition is true otherwise it will throw TimeoutException, It never returns null.

So if your using ExpectedConditions.elementToBeClickable to find an element which will always gives you the clickable element, so no need to check for null condition, you should try as below :-

WebDriverWait wait = new WebDriverWait(Scenario1Test.driver, 10); 
WebElement element = wait.until(ExpectedConditions.elementToBeClickable(By.xpath("(//div[@id='brandSlider']/div[1]/div/div/div/img)[50]")));
element.click();

As you are saying element.click() passes both on link and label that's doesn't mean element is not clickable, it means returned element clicked but may be there is no event performs on element by click action.

Note:- I'm suggesting you always try first to find elements by id, name, className and other locator. if you faced some difficulty to find then use cssSelector and always give last priority to xpath locator because it is slower than other locator to locate an element.

Hope it helps you..:)

https://stackoverflow.com/questions/38327049/check-if-element-is-clickable-in-selenium-java

Don't use driver.close() on the particular page, let it be and use the code below in driver factory:

//This closes the browser after each test class 

@AfterClass
public void tearDown()
{
    driver.quit();
}

It should help.

https://stackoverflow.com/questions/45677880/kill-chromedriver-process-in-selenium-java

Blogs

Check out the latest blogs from LambdaTest on this topic:

E2E Testing tutorial: Complete Guide to End to End Testing With Examples

E2E Testing also called End to End testing, is a very common testing methodology where the objective is to test how an application works by checking the flow from start to end. Not only the application flow under dev environment is tested, but the tester also has to check how it behaves once integrated with the external interface. Usually, this testing phase is executed after functional testing and system testing is completed. The technical definition of end to end testing is – a type of testing to ensure that behavioural flow of an application works as expected by performing a complete, thorough testing, from the beginning to end of the product-user interaction in order to realize any dependency or flaw in the workflow of the application.

17 Skills Of Highly Effective Software Testers

Software testing is an essential process for developing the perfect app. But, as a software tester, it is essential to have certain skills which in turn will help with testing the applications better.

Common Mistakes Made By Web Developers And How To Avoid Them

Ever-since the introduction of World Wide Web in 1990, the domain of web development has evolved dynamically from web pages to web applications. End users no longer browse web pages for reading static content. Websites now have dynamic features to increase their engagement rate. Interactive websites are being developed using which users can perform their day to day activities like shopping for groceries, banking, paying taxes, etc. However, these applications are developed by human beings, and mistakes are supposed to happen. Often a simple mistake can impact a critical functionality in your website that will lead the user to move away to a different website, reducing your profit and SERP ranking. In this article, we shall discuss the common mistakes made by developers while developing a web application.

Why Vertical Text Orientation Is A Nightmare For Cross Browser Compatibility?

The necessity for vertical text-orientation might not seem evident at first and its use rather limited solely as a design aspect for web pages. However, many Asian languages like Mandarin or Japanese scripts can be written vertically, flowing from right to left or in case of Mongolian left to right. In such languages, even though the block-flow direction is sideways either left to right or right to left, letters or characters in a line flow vertically from top to bottom. Another common use of vertical text-orientation can be in table headers. This is where text-orientation property becomes indispensable.

Using Selenium and Python Hypothesis for Automation Testing

This article is a part of our Content Hub. For more in-depth resources, check out our content hub on Selenium Python Tutorial.

Selenium 4 Tutorial:

LambdaTest’s Selenium 4 tutorial is covering every aspects of Selenium 4 testing with examples and best practices. Here you will learn basics, such as how to upgrade from Selenium 3 to Selenium 4, to some advanced concepts, such as Relative locators and Selenium Grid 4 for Distributed testing. Also will learn new features of Selenium 4, such as capturing screenshots of specific elements, opening a new tab or window on the browser, and new protocol adoptions.

Chapters:

Upgrading From Selenium 3 To Selenium 4?: In this chapter, learn in detail how to update Selenium 3 to Selenium 4 for Java binding. Also, learn how to upgrade while using different build tools such as Maven or Gradle and get comprehensive guidance for upgrading Selenium.
What’s New In Selenium 4 & What’s Being Deprecated? : Get all information about new implementations in Selenium 4, such as W3S protocol adaption, Optimized Selenium Grid, and Enhanced Selenium IDE. Also, learn what is deprecated for Selenium 4, such as DesiredCapabilites and FindsBy methods, etc.
Selenium 4 With Python: Selenium supports all major languages, such as Python, C#, Ruby, and JavaScript. In this chapter, learn how to install Selenium 4 for Python and the features of Python in Selenium 4, such as Relative locators, Browser manipulation, and Chrom DevTool protocol.
Selenium 4 Is Now W3C Compliant: JSON Wireframe protocol is retiring from Selenium 4, and they are adopting W3C protocol to learn in detail about the advantages and impact of these changes.
How To Use Selenium 4 Relative Locator? : Selenium 4 came with new features such as Relative Locators that allow constructing locators with reference and easily located constructors nearby. Get to know its different use cases with examples.
Selenium Grid 4 Tutorial For Distributed Testing: Selenium Grid 4 allows you to perform tests over different browsers, OS, and device combinations. It also enables parallel execution browser testing, reads up on various features of Selenium Grid 4 and how to download it, and runs a test on Selenium Grid 4 with best practices.
Selenium Video Tutorials: Binge on video tutorials on Selenium by industry experts to get step-by-step direction from automating basic to complex test scenarios with Selenium.