How to use getCurrentUrl method of org.openqa.selenium.support.events.EventFiringWebDriver class

The basic authentication via url is blocked only for sub resources. So you could still use it on the domain:

driver.get("http://admin:admin@localhost:8080");
driver.get("http://localhost:8080/project");

You could also create a small extension to automatically set the credentials when they are requested:

options = webdriver.ChromeOptions()
options.add_extension(r'C:\dev\credentials.zip')

https://gist.github.com/florentbr/25246cd9337cebc07e2bbb0b9bf0de46

You can't rely on sleeps so you should try this:

WebElement myDynamicElement = (new WebDriverWait(driver, 10))
  .until(ExpectedConditions.presenceOfElementLocated(By.id("myDynamicElement")));

You have a plenty of methods in the ExpectedConditions class.

Here is some info:

• http://docs.seleniumhq.org/docs/04_webdriver_advanced.jsp

Hope you find this useful.

Yes, that's the default behavior of TestNG and I had introduced it through that pull request to fix the bug https://github.com/cbeust/testng/issues/2022

To set the JVM arguments in intelliJ, choose Run > Edit Configurations, and add this JVM argument in the VM options section after -ea (which would be there by default.

For more information on editing configurations, please refer to the official documentation here

Added screenshot for easy to find in Intellij

Argument value

-ea -Dtestng.dtd.http=true

If the above does not work do at template level, this will fix it, which is

Run--> Edit configuration --> template --> testng

Try:

webElement.findElement(By.cssSelector("#endDate")).getAttribute("value")

Or:

webElement.findElement(By.cssSelector("#endDate")).getText()

You have to try it out. It depends on your special case. If these variants don't work, check if your selectors are correct.

If all of them didn't work, try to get the value over angular.element as below:

return (String) ((JavascriptExecutor) this.webDriver).executeScript("angular.element($('#endDate')).text()");

#getText()

getText() delivers the innerText of a WebElement.

Your input field does not have any inner Text. The text is found inside your value-attribute, hence accessing it via getAttribute("value") is the correct way to do it.

Several possible approaches:

1. Use dbunit, which is designed to return a database to a know state between tests.
2. Wrap each test in a database transaction with a try{} finally{} block where the finally rolls back the transaction.
3. Use a database strictly for testing and don't worry about it. Make your tests create uniquely identified / named values each time so you don't have conflicts, but otherwise don't take any action.

PhantomJS uses different mechanism in setting capabilities

static ArrayList<String> cliArgsCap = new ArrayList<String>();
capabilities = DesiredCapabilities.phantomjs();
cliArgsCap.add("--web-security=false");
cliArgsCap.add("--ssl-protocol=any");
cliArgsCap.add("--ignore-ssl-errors=true");
capabilities.setCapability("takesScreenshot", true);
capabilities.setCapability(
    PhantomJSDriverService.PHANTOMJS_CLI_ARGS, cliArgsCap);
capabilities.setCapability(
    PhantomJSDriverService.PHANTOMJS_GHOSTDRIVER_CLI_ARGS,
        new String[] { "--logLevel=2" });
this.driver = new PhantomJSDriver(capabilities);

For more information about its command line, you could reference http://phantomjs.org/api/command-line.html

This should work:

driver.findElement(By.LinkText("Users")).click();

By LinkText is possible

You can try with 127.0.0.1 instead of localhost.

Setting a domain cookie on local host is no longer supported by Chrome. If you remove the domain from the cookie settings, it should work correctly.

More details:

The current WebDriver standard isn't clear on how cookie domain should be handled. ChromeDriver's implementation attempts to follow https://www.rfc-editor.org/rfc/rfc6265#section-5.3. According to item 6 of the cookie storage model, specifying a cookie domain results in a domain cookie, while not specifying the domain results in a host-only cookie. However, creating a domain cookie for localhost doesn't really make sense, as localhost doesn't following the domain naming conventions. Chrome used to be lenient with this, but Chrome 77 now has code to reject creating domain cookie for localhost, so specifying domain for localhost cookie is no longer allowed.