How to use perform method of org.openqa.selenium.interactions.ContextClickAction class

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
    }
}

Given you have maven tag my expectation is that your project is being managed by Maven hence built by Maven Compiler Plugin so your IDE language level settings might derive from what is defined in the pom.xml

I would recommend setting project language level in:

1. Maven pom.xml file like:

   <properties>
       <maven.compiler.source>1.8</maven.compiler.source>
       <maven.compiler.target>1.8</maven.compiler.target>
   </properties>    
   

2. In Idea on Project Properties page you can choose the Language Level for each module

   

More information:

• Selenium Webdriver Tutorial with JAVA: How to set up a TestNG maven based project from scratch
• stop IntelliJ IDEA to switch java language level every time the pom is reloaded (or change the default project language level)

Here is an explanation of what is happening:

You are calling driver.close() in RegisterNewUser. This will close the current window. If no open windows remain, the driver quits. So, when your tearDown calls driver.quit() the session has already ended and you get an error.

Solutions you could use:

• don't call driver.close() in your test and let the teardown handle it

or

• in teardown, check for a valid session and only call driver.quit() if one exists

You can perform any action on driver object, if it is throwing UnreachableBrowserException, then there is problem to communicate with the browser.

The most common causes for this exception are:

1. The provided server address to RemoteWebDriver is invalid, so the connection could not be established.
2. The browser has died mid-test.

And you can call the following method to verify the browser is closed or not.

public boolean isBrowserClosed(WebDriver driver)
{
    boolean isClosed = false;
    try {
        driver.getTitle();
    } catch(UnreachableBrowserException ubex) {
        isClosed = true;
    }

    return isClosed;
}

isElementPresent() - This method basically tests if the element we are looking for is present somewhere on the page.

isVisible() - looks for display: none style tag - this might throw a null pointer if we aren't careful...thus to see if an element is visible first check if the element is present using isElementPresent() method. Then try checking if the element is visible!

Observe that isElementPresent() won't mind even if our element is not visible.

For ex: lets say the below is the html code for a component on my test application:

now if you test the above component with

selenium.isElementPresent("testinput") - returns true!
selenium.isVisible("testinput") - returns false!

It is actually possible to scroll automatically to element. Although this is not a good solution in this case (there must be a way to get it working without scrolling) I will post it as a workaround. I hope someone will come up with better idea...

public void scrollAndClick(By by)
{
   WebElement element = driver.findElement(by);
   int elementPosition = element.getLocation().getY();
   String js = String.format("window.scroll(0, %s)", elementPosition);
   ((JavascriptExecutor)driver).executeScript(js);
   element.click();
}

Create a new implementation of FieldDecorator.

When you use the PageFactory you are probably calling

 public static void initElements(ElementLocatorFactory factory, Object page)

This would become

 public static void initElements(FieldDecorator decorator, Object page)

Your FieldDecorator could behave similarly to the DefaultFieldDecorator except wrap the proxy in your custom type.

See the classes here [source]

You want to wait until the alert is present before switching to it, similar to your 3rd row. Reference.

EDIT: try:

new WebDriverWait(driver, 60)
        .ignoring(NoAlertPresentException.class)
        .until(ExpectedConditions.alertIsPresent());

Alert al = driver.switchTo().alert();
al.accept();

You can use WebDriverWait. From docs example:

 (new WebDriverWait(driver, 10)).until(new ExpectedCondition<Boolean>() {
            public Boolean apply(WebDriver d) {
                return d.findElement(...).getText().length() != 0;
            }
        });