How to use hashCode method of org.openqa.selenium.remote.Command class

I found the work around as below

1. Open terminal
2. Navigate to path where your chromedriver file is located
3. Execute any one of the below commands

Command1: xattr -d com.apple.quarantine <name-of-executable>

Example

/usr/local/Caskroom/chromedriver 
$ xattr -d com.apple.quarantine chromedriver 

(or)

Command2: spctl --add --label 'Approved' <name-of-executable>

Source: https://docwhat.org/upgrading-to-catalina

Note: This will work only with the file(s) where the above command is executed. If a new chromedriver is downloaded then the command has to be executed again on the newly downloaded file

Aditya,

As you said in your last comment that you are trying to access chrome of some other system so based on that you should keep your chrome driver in that system itself.

for example: if you are trying to access linux chrome from windows then you need to put your chrome driver in linux at some place and give permission as 777 and use below code at your windows system.

System.setProperty("webdriver.chrome.driver", "\\var\\www\\Jar\\chromedriver");
Capability= DesiredCapabilities.chrome();   Capability.setPlatform(org.openqa.selenium.Platform.ANY);
browser=new RemoteWebDriver(new URL(nodeURL),Capability);

This is working code of my system.

You will have to download the "Selenium Client & WebDriver Language Bindings" for Java from Selenium Downloads. You can download directly by clicking the link here.

Include all the JAR files that are present in the downloaded ZIP file. To include multiple JARs in Java classpath, you can check the link here.

The selenium-server-standalone JAR is required if you are running your tests locally. Executing the command java -jar selenium-server-standalone-2.48.2.jar will start a Selenium server, which required to launch Selenium tests locally. You need not use it, if you are running tests on BrowserStack.

Would also recommend using an IDE for Java. The most commonly recommended ones are IntelliJ Idea, Eclipse, and Netbeans.

You can get immediate parent using ..

By.xpath("//input[contains(@id,'custProglabel')]/..")

As a side note, xpath should start with lower case 'x'.

Your assumption "... ExpectedConditions.visibilityOf(WebElement) would find the first element visible." is wrong! You will need to declare your WebElement as a List, find all of them, and pick the one that is visible. Here is a sample that I used successfully in the past:

@FindBy(xpath = "//input[@ng-model='loginData.username']")
private List<WebElement> txtUsername;

public String getUsername() {
    driverWait.until(CustomExpectedConditions.presenceOfAllElements(txtUsername));
    for (WebElement oneUsername : txtUsername) {
        if (oneUsername.isDisplayed())
            return oneUsername.getAttribute("value");
    }
    return null;
}

public void setUsername(String username) {
    driverWait.until(CustomExpectedConditions.presenceOfAllElements(txtUsername));
    for (WebElement oneUsername : txtUsername) {
        if (oneUsername.isDisplayed()) {
            oneUsername.clear();
            oneUsername.sendKeys(username);
            break;
        }
    }
}

Based on discussion elsewhere, here is the CustomExpectedConditions:

public class CustomExpectedConditions {
    /**
     * Based on {@link ExpectedConditions#presenceOfAllElementsLocatedBy(org.openqa.selenium.By)}.
     * 
     * @param elements
     * @return
     */
    public static ExpectedCondition<List<WebElement>> presenceOfAllElements(
            final List<WebElement> elements) {
        return new ExpectedCondition<List<WebElement>>() {

            @Override
            public List<WebElement> apply(WebDriver driver) {
                // List<WebElement> elements = findElements(locator, driver);
                return elements.size() > 0 ? elements : null;
            }
        };
    }
}

While working with Selenium v3.11.x, GeckoDriver v0.20.0 and Firefox Quantum v59.0.2 there are different option to invoke a new/existing Firefox Profile

If you are looking to use a new Firefox Profile on every run of your Test Execution you can use the following code block :

System.setProperty("webdriver.gecko.driver", "C:\\path\\to\\geckodriver.exe");
FirefoxOptions options = new FirefoxOptions();
options.setProfile(new FirefoxProfile());
WebDriver driver = new FirefoxDriver(options);
driver.get("https://www.google.com");

If you are looking to use an existing Firefox Profile on every run of your Test Execution first you have to create a Firefox Profile manually following the instructions at Creating a new Firefox profile on Windows.

Now you have 2 ways to invoke the Firefox Profile you have created as follows :

• You can use the FirefoxOptions class to invoke the existing Firefox Profile and you can use the following code block :

  System.setProperty("webdriver.gecko.driver", "C:\\path\\to\\geckodriver.exe");
  ProfilesIni profile = new ProfilesIni();
  FirefoxProfile testprofile = profile.getProfile("debanjan");
  FirefoxOptions opt = new FirefoxOptions();
  opt.setProfile(testprofile);
  WebDriver driver =  new FirefoxDriver(opt);
  driver.get("https://www.google.com");
  

• You can also use the DesiredCapabilities class to set the existing Firefox Profile and later merge within an instance of FirefoxOptions and you can use the following code block :

  System.setProperty("webdriver.gecko.driver", "C:\\path\\to\\geckodriver.exe");
  ProfilesIni profile = new ProfilesIni();
  FirefoxProfile testprofile = profile.getProfile("debanjan");
  DesiredCapabilities dc = DesiredCapabilities.firefox();
  dc.setCapability(FirefoxDriver.PROFILE, testprofile);
  FirefoxOptions opt = new FirefoxOptions();
  opt.merge(dc);
  WebDriver driver =  new FirefoxDriver(opt);
  driver.get("https://www.google.com");
  

Attribute validationMessage will return the message, that will be showing if validation fails:

WebElement username = driver.findElement(By.name("uname"));    
String validationMessage = username.getAttribute("validationMessage");

If element has required attribute, browser will show the message after submitting the form:

boolean required = Boolean.parseBoolean(username.getAttribute("required"));

You can check whether entered value is valid:

boolean valid = (Boolean)((JavascriptExecutor)driver).executeScript("return arguments[0].validity.valid;", username);

---

Not: message text and validation is customizable. If you want to test customized validation and message.

Here test code for custom validation(Java, TestNG):

Assert.assertTrue(Boolean.parseBoolean(username.getAttribute("required")), "Username is required and message should be showin");
Assert.assertEquals(username.getAttribute("validationMessage"), "My custom message", "Message text control");

username.sendKeys("@vasya ");
Assert.assertTrue((Boolean)((JavascriptExecutor)driver).executeScript("return arguments[0].validity.valid;", username), "Username has special characters");

However, I am unsure how the method determines equality?

The driver generates a reference for each encountered HTMLElement object in the document and always returns the same reference for an HTMLElement object.

This reference is stored in the WebElement.id property on the client side and has nothing to do with the id attribute used with a locator.

So to determine the equality between two WebElement, the client simply tests the reference stored in WebElement.id.

And are there any circumstances where the two web elements are in fact the same but the method shows they are different?

Technically speaking, no it never happens and it would be a serious issue if it was the case.

But it kind of depends on what you mean by the same. For instance a button can look the same at two different moments, but may have been replaced by an identical one which would generate a new reference. This is the case when the page or some parts are reloaded:

  driver.get("http://stackoverflow.com/");

  WebElement elementA = driver.findElement(By.cssSelector("#logo"));
  WebElement elementB = driver.findElement(By.cssSelector("#logo"));

  boolean same1 = elementA.equals(elementB);  // return true

  elementB.click();  // reloads the page, all the previous web element are now obsolete

  WebElement elementC = driver.findElement(By.cssSelector("#logo"));

  boolean same2 = elementA.Equals(elementC);  // return false

Yes, as what Richard says, this is a duplicate of How to input text into tinceMCE editior using selenium/webdriver.

For your specific code, I'd suggest

• Try different locator for mceContentBody, e.g use By.cssSelector(".mceContentBody"), By.cssSelector("body"), etc.

• Click the body first before sending keys.

driver.findElement(By.tagName("body")).click().sendKeys("YOOOO");

• Set innerHTML

inputWebDriver.switchTo().frame("input-data_ifr");
WebElement element = inputWebDriver.findElement(By.cssSelector("body"));
(JavascriptExecutor)driver.executeScript("arguments[0].innerHTML = '<h1>Set text using innerHTML</h1>'", element);

• Use TinyMCE's native API

// no need to switch iframe
(JavascriptExecutor)driver.executeScript("tinyMCE.activeEditor.setContent('<h1>Native API text</h1> TinyMCE')");

Further reading: Test WYSIWYG editors using Selenium WebDriver