In my TestNG framework with Java and Selenium, I have created two custom methods to handle WebElement interactions. Here they are:
// Checks if a WebElement is present on the screen
public boolean isElementPresent(WebElement element) {
try {
element.isDisplayed();
return true;
} catch (RuntimeException e) {
return false;`
}
}
// Used to click on the desired element
public void clickWebElement(WebElement element) {
isElementPresent(element);
element.click();
}
protected void enterDataintoField(WebElement element,String fieldData) {
isElementPresent(element);
element.click();
element.clear();
element.sendKeys(fieldData);
}
Let's consider a scenario where clicking on a "Login" link opens a page with username, password fields, and a logout button. Below is a sample code for logging in:
public void login(String username, String password)
{
try{
clickWebElement(Login);
//pause few seconds for page load
enterDataintoField(username, "Adam");
enterDataintoField(password, "mypassword");
//pause few seconds to login
Assert.assertTrue(isElementPresent(logoutBtn));
}catch({**ErrorType**} e){
//Some code here
}
}
The dilemma arises when deciding the exception handling strategy. Using RuntimeException won't catch assert failures but does well with other issues. On the contrary, using AssertionError catches assert failures but not other exceptions. How can I tackle this efficiently without cluttering my code with multiple catch blocks?
Your suggestions and best practices would be highly appreciated.