How to use builder method of org.openqa.selenium.ie.InternetExplorerDriver class

If you are using Webdriver then the item you are looking for is Selected.

Often times in the render of the checkbox doesn't actually apply the attribute checked unless specified.

So what you would look for in Selenium Webdriver is this

isChecked = e.findElement(By.tagName("input")).Selected;

As there is no Selected in WebDriver Java API, the above code should be as follows:

isChecked = e.findElement(By.tagName("input")).isSelected();

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

It is because you can't open local resources programmatically. Chrome raises an error:

Not allowed to load local resource: chrome://downloads/

Working solution is to run Chrome with following flags:

--disable-web-security --user-data-dir="C:\chrome_insecure"

But this trick doesn't work with Selenium Chrome Driver(I don't know actually why, a tried to remove all args that appears in chrome://version, but this doesn't helps).

So for me above solution is the only one that works:

C# example:

driver.Navigate().GoToUrl("chrome://downloads/")

There is another trick if you need to open downloaded file:

JavaScript example:

document.getElementsByTagName("downloads-manager")[0].shadowRoot.children["downloads-list"]._physicalItems[0].content.querySelectorAll("#file-link")[0].click()

Chrome uses Polymer and Shadow DOM so there is no easy way to query #file-link item.

Also you need to execute .click() method with JavaScript programatically because there is a custom event handler on it, which opens actual downloaded file instead of href attribute which point to url where you downloaded file from.

Try this one.

String xpath= "//*[@name='" + Category[index] + "']";   
driver.findElement(By.xpath(xpath)).click();

The main problem is at this line:

driver.findElement(By.cssSelector("a:contains('About Google')"));

css doesn't maintain contains() for Selenium WD - See here.

For using contains() you have to use Xpath.

With Xpath your locator will be:

//a[contains(text(), 'About Google')]

and for driver it will be as:

driver.findElement(By.xpath("//a[contains(text(), 'About Google')]"));

For finding links with Selenium you can use:

driver.findElement(By.linkText("your link name here"));

It is limitation of CSS selectors compare to Xpath:

• you can't take parent element with CSS selectors (Xpath has XPath axes)
• you can't use contains (it is only XPath privilege).

BTW
For processing Xpath locators from page you able to use extension for Firefox browser:

• FirePath

• Xpath Checker

You are using latest version of Selenium WebDriver i.e. Selenium 3.x, this version of webdriver doesn't support direct firefox launch. You have to set the SystemProperty for webdriver.gecko.driver.

Replace the Code:-

WebDriver driver;
driver =new FirefoxDriver();

With This code:-

WebDriver driver;
System.setProperty("webdriver.gecko.driver", "<Path to your WebDriver>");
driver =new FirefoxDriver();

You can get the information about latest changes here

You can download the latest Gecko driver from here

Because TeamCity build agents are run as a Windows service. So you won't be able to see the actual GUI.

If you want to change it, please change your build agent installation.

• Installing and Configuring the TeamCity Server
• How can I run a Windows GUI application on as a service?
• Selenium Tests run in the background when TeamCity CI is run as a Windows service
• Running Automated GUI tests with TeamCity

The easiest way is to reference a static factory method via its fully qualified method name -- for example, @MethodSource("example.Testing#text()").

To simplify matters even further, you can introduce a custom composed annotation that combines the configuration for @ParameterizedTest and @MethodSource like this:

import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;

import org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.MethodSource;

@Target(ElementType.METHOD)
@Retention(RetentionPolicy.RUNTIME)
@ParameterizedTest
@MethodSource("example.Testing#text()")
public @interface ParameterizedTextTest {
}

You can then reuse that like this:

package example;

import org.junit.jupiter.api.Nested;

class Testing {

    static String[] text() {
        return new String[] { "A", "B" };
    }

    @Nested
    class NestedTesting {

        @ParameterizedTextTest
        void testA(String text) {
            System.out.println(text);
        }

        @ParameterizedTextTest
        void testB(String text) {
            System.out.println(text);
        }
    }
}

Happy testing!

As per Selenium documentation,

• The version v4.0.0-rc-1 supports CDP versions: 85, 92, 93.

But you are using 94 version of Chrome and ChromeDriver. So please update your dependencies to latest version v4.0.0-rc-2

Dependency:

<dependency>
    <groupId>org.seleniumhq.selenium</groupId>
    <artifactId>selenium-java</artifactId>
    <version>4.0.0-rc-2</version>
</dependency>

Reference: https://github.com/SeleniumHQ/selenium/blob/trunk/java/CHANGELOG