For Chromedriver try out with:

String downloadFilepath = "/path/to/download";
HashMap<String, Object> chromePrefs = new HashMap<String, Object>();
chromePrefs.put("profile.default_content_settings.popups", 0);
chromePrefs.put("download.default_directory", downloadFilepath);
ChromeOptions options = new ChromeOptions();
options.setExperimentalOption("prefs", chromePrefs);
DesiredCapabilities cap = DesiredCapabilities.chrome();
cap.setCapability(CapabilityType.ACCEPT_SSL_CERTS, true);
cap.setCapability(ChromeOptions.CAPABILITY, options);
WebDriver driver = new ChromeDriver(cap);

Note:- Use File.separator to handle slashes, it will put syntax as per os it is executing the code. In windows you need to use \\ for path while if you are using linux or mac then use //

Hope this helps. :)

The desired element is inside an iframe, you need to switch to it before making a search:

driver.switchTo().frame("cboxform");

driver.findElement(By.id("tblmid"));

See also:

• How to switch between frames in Selenium WebDriver using Java

You've got two concerns to worry about. The first is making sure you've different browsers for each user, and the second is running the two users concurrently. There are a couple of different ways to do each of them, so I'll look at them separately.

Managing two browsers

The first part, that of opening two browsers, isn't too difficult; You can just create a separate WebDriver object for each one. You may have to use two different browsers, however, to avoid any kind of session sharing issues:

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.firefox.FirefoxDriver;
import org.openqa.selenium.chrome.ChromeDriver;

WebDriver user_1 = new FirefoxDriver();
WebDriver user_2 = new ChromeDriver();

If you need to open two instances of the same browser, your best option is to use Selenium Grid to host your desired browsers, and then creating remote connections to them:

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.remote.RemoteWebDriver;
import org.openqa.selenium.remote.DesiredCapabilities;

DesiredCapabilities capabilities = DesiredCapabilities.firefox();
URL server = new URL("http://your-server-location.com");
WebDriver driver = new RemoteWebDriver(server, capabilities);

If you don't want to set up your own Selenium Grid, you can use a service like Sauce Labs to manage it for you (and also give you an easy way to add extra test platform resources).

Managing two users simultaneously

It sounds like you can just have the one test class performing each action in turn against the relevant Webdriver. Use something like the Page Object Model to provide service objects representing your pages, which you can pass an instance of WebDriver too. Then, you can express your test logic more fluently rather then dealing with different webdrivers and elements:

public class Chatsite{
  public WebDriver driver;
  private WebElement talkbox;
  private WebElement chatlog;
  private WebElement sendbutton;

  public Chatsite(WebDriver passed_in_driver){
      driver = passed_in_driver;
      talkbox = driver.find_element("name", "talkbox");
      sendbutton = driver.find_element("name", "send");
      chatlog = driver.find_element("name", "chatlog");
      driver.get("http://www.yoursite.com");
  }

  public void say(String string_to_type){
      talkbox.send_keys(string_to_type);
      sendbutton.click();
  }

  public void sees_in_the_chatlog(String expected_content){
      String current_chat_text =  chatlog.getText();
      assertTrue("Couldn't find content", current_chat_text.contains(expected_content));
  }
}

#Now, in your tests
#Name your users so it's easier to keep track of them
Chatsite david = Chatsite.new(user_1);
Chatsite susan = Chatsite.new(user_2);

david.say("Isn't it a fine day?");
susan.sees_in_the_chatlog("Isn't it a fine day?");

susan.say("If you're going to talk about the weather I'm failing this test case");
## And so on in that fashion

for (String handle : driver.getWindowHandles()) {
    driver.switchTo().window(handle);
    System.out.println(String.format("handle: %s, url: %s", handle, driver.getWebDriver().getCurrentUrl()));
} 

You are right in your analysis, @Befores and @Afters are added to the list of Statements before any Rules. The @Before gets executed after the @Rule and the @After gets executed before the @Rule. How you fix this depends on how flexible you can be with SeleniumBaseTestCaseWithCompany.

The easiest way would be to remove your @Before/@After methods and replace them with an ExternalResource. This could look something like:

public class BeforeAfterTest {
    @Rule public TestRule rule = new ExternalResource() {
        protected void before() throws Throwable { System.out.println("externalResource before"); }
        protected void after() { System.out.println("externalResource after"); }
    };

    @Test public void testHere() { System.out.println("testHere"); }
}

this gives:

externalResource before
testHere
externalResource after

This field can be put into your base class, so it gets inherited/overridden. Your problem with ordering between @After and your rules then goes away, because you can order your rules how you like, using @RuleChain (in 4.10, not 4.8).

If you can't change SeleniumBaseTestCaseWithCompany, then you can extend BlockJUnit4ClassRunner, but don't override withAfters, but override BlockJUnit4ClassRunner#methodBlock(). You can then call super.methodBlock, and reorder the Statements as necessary[*].

[*]You could just copy the code, and reorder the lines, but withRules is private and therefore not callable from a subclass.

You can use JavaScriptExecutor for scrolling.

Scroll Down

((JavascriptExecutor)driver).executeScript("window.scrollTo(0,document.body.scr‌​ollHeight);");

Scroll Up

((JavascriptExecutor)driver).executeScript("window.scrollTo(0,0);");

Compile like so:

javac -classpath selenium-server-standalone-2.20.0.jar Example.java

Unless you put the Java file in the org.openqa.selenium.example, you will have to remove the package specifier. Run the compiled file like so:

java -cp .:selenium-server-standalone-2.20.0.jar Example

This chains the current directory to the classpath.

ElementNotInteractableException

ElementNotInteractableException is the W3C exception which is thrown to indicate that although an element is present on the HTML DOM, it is not in a state that can be interacted with.

Reasons & Solutions :

The reason for ElementNotInteractableException to occur can be numerous.

1. Temporary Overlay of other WebElement over the WebElement of our interest :

   In this case, the direct solution would have been to induce ExplicitWait i.e. WebDriverWait in combination with ExpectedCondition as invisibilityOfElementLocated as folllows:

   WebDriverWait wait2 = new WebDriverWait(driver, 10);
   wait2.until(ExpectedConditions.invisibilityOfElementLocated(By.xpath("xpath_of_element_to_be_invisible")));
   driver.findElement(By.xpath("xpath_element_to_be_clicked")).click();
   

   A better solution will be to get a bit more granular and instead of using ExpectedCondition as invisibilityOfElementLocated we can use ExpectedCondition as elementToBeClickable as follows:

   WebDriverWait wait1 = new WebDriverWait(driver, 10);
   WebElement element1 = wait1.until(ExpectedConditions.elementToBeClickable(By.xpath("xpath_of_element_to_be_clicked")));
   element1.click();
   

2. Permanent Overlay of other WebElement over the WebElement of our interest :

   If the overlay is a permanent one in this case we have to cast the WebDriver instance as JavascriptExecutor and perform the click operation as follows:

   WebElement ele = driver.findElement(By.xpath("element_xpath"));
   JavascriptExecutor executor = (JavascriptExecutor)driver;
   executor.executeScript("arguments[0].click();", ele);
   

Use profiles!

from selenium import webdriver

options = webdriver.ChromeOptions()
options.add_argument(r"user-data-dir=D:\Python\Memory\WebWhatsAppBot")

navegador = webdriver.Chrome(
executable_path="D:\Python\WebWhatsAppBot\chromedriver.exe", chrome_options=options)
navegador.get("https://web.whatsapp.com/")