How to use getEnabledLogTypes method of org.openqa.selenium.logging.LoggingPreferences class

As your trying to verify the input node is enabled or disabled, isEnabled() checks for the disabled attribute on the element. If the attribute "disabled" is not present, it returns True.

Try the below code:

@FindBy(xpath = "//label[contains(@class, 'CheckboxTextAligned')]/following::input")
private List<WebElement> airportListCheckbox;

public void getEnabledValues() {
for (WebElement elements : airportListCheckbox) {
    if(elements.isEnabled()) {
        for (WebElement airportText : airportListTextName) {
        airportText.getText();
        LOG.info(airportText.getText());                
        }
    }       
}

As you want to check the input node is enabled or not, you need to change your locator a bit because previosly you are try to check the label is enabled/disabled not the input node So you are getting always true.

A few quick searches led me to this:

http://blogs.steeplesoft.com/posts/2012/grabbing-screenshots-of-failed-selenium-tests.html

Basically, he recommends creating a JUnit4 Rule that wraps the test Statement in a try/catch block in which he calls:

imageFileOutputStream.write(
    ((TakesScreenshot) driver).getScreenshotAs(OutputType.BYTES));

Does that work for your problem?

This is exactly as expected. If your class name includes a space, WebDriver will see it as a "compound selector". You can either remove the space in your By.className() locator, which should still find the elements you're looking for; or you can move to finding by CSS selectors, using something like By.cssSelector(".cashout_noCash"), which offer far more flexibility for similar functionality. This is exactly what the exception message says.

This should do the trick:

driver.switchTo().alert().accept();

You can kill the Browser instance initiated using Selenium retriving the PID from the capabilities object and then invoking getRuntime() with taskkill /PID as follows:

• Code Block:

  import java.io.IOException;
  import org.openqa.selenium.Capabilities;
  import org.openqa.selenium.WebDriver;
  import org.openqa.selenium.firefox.FirefoxDriver;
  import org.openqa.selenium.remote.RemoteWebDriver;
  
  public class Kill_Firefox_PID {
  
      public static void main(String[] args) throws IOException {
  
          System.setProperty("webdriver.gecko.driver", "C:\\Utility\\BrowserDrivers\\geckodriver.exe");
          WebDriver driver = new FirefoxDriver();
          Capabilities cap = ((RemoteWebDriver) driver).getCapabilities();
          System.out.println("moz:processID value is : "+cap.getCapability("moz:processID"));
          Runtime.getRuntime().exec("taskkill /PID "+cap.getCapability("moz:processID"));
      }
  }
  

• Console Output:

  moz:processID value is : 8492
  

Just from the error message, it looks like your -jar argument has something other than - as the first character, probably an en-dash. It would then interpret –jar as a class to search for on the class path. Attempting this yields the same error message for me, modulo whatever encoding transformation is happening to the error message on your system.

You can use the dependsOnMethods or dependsOnGroups annotation parameter in your other test methods:

@Test(dependsOnMethods = {"stopTestingIfThisFailed"})
public void testAnotherTestMehtod()  {

}

JavaDoc of the dependsOnMethods parameter:

The list of methods this method depends on. There is no guarantee on the order on which the methods depended upon will be run, but you are guaranteed that all these methods will be run before the test method that contains this annotation is run. Furthermore, if any of these methods was not a SUCCESS, this test method will not be run and will be flagged as a SKIP. If some of these methods have been overloaded, all the overloaded versions will be run.

See https://testng.org/doc/documentation-main.html#dependent-methods

Try setting an implicit wait of maybe 10 seconds.

gmail.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS);

Or set an explicit wait. An explicit waits is code you define to wait for a certain condition to occur before proceeding further in the code. In your case, it is the visibility of the password input field. (Thanks to ainlolcat's comment)

WebDriver gmail= new ChromeDriver();
gmail.get("https://www.gmail.co.in"); 
gmail.findElement(By.id("Email")).sendKeys("abcd");
gmail.findElement(By.id("next")).click();
WebDriverWait wait = new WebDriverWait(gmail, 10);
WebElement element = wait.until(
ExpectedConditions.visibilityOfElementLocated(By.id("Passwd")));
gmail.findElement(By.id("Passwd")).sendKeys("xyz");

Explanation: The reason selenium can't find the element is because the id of the password input field is initially Passwd-hidden. After you click on the "Next" button, Google first verifies the email address entered and then shows the password input field (by changing the id from Passwd-hidden to Passwd). So, when the password field is still hidden (i.e. Google is still verifying the email id), your webdriver starts searching for the password input field with id Passwd which is still hidden. And hence, an exception is thrown.

Although this is an old question and the OP has most probably solved it, it came up first in a google search for same issue and I thought to add my solution in case it helps anyone.

For poi 4.1.7 I used font.setBold( true ) instead of font.setBoldweight( Font.BOLDWEIGHT_BOLD )

To put it into the context of the post's question, the author could change their code

From: headerFont2.setBoldweight(Font.BOLDWEIGHT_BOLD);

To: headerFont.font.setBold( true );

Given that they have also imnported Font class:

import org.apache.poi.ss.usermodel.Font;