Did you know that if the element variable name is the same with the element id or element name, it's not mandatory to use FindBy annotation as these are known as Direct Locators?
Like this:
public class FindByExample {
private WebDriver driver;
@FindBy(id = "username") //here the text box has the locator id=username.
private WebElement uname;
@FindBy(name = "password") //here the text box has the locator name=password.
private WebElement pwd;
public FindByExample(WebDriver driver) {
this.driver = driver;
PageFactory.initElements(driver, this);
}
The above code can be written with NO FindBy annotations if the web element variables have the same name or ID:
public class FindByExample {
private WebDriver driver;
private WebElement username;
private WebElement password;
public FindByExample(WebDriver driver) {
this.driver = driver;
PageFactory.initElements(driver, this);
}
selenium easierWay tipsAndTricks # testautomation seleniumAutomation FindBy PageFactory
At times, we see some weird behavior in your testNG execution and feel that the information displayed is insufficient and would like to see more details. At other times, the output on the console is too verbose and we may want to only see the errors. This is where a verbose attribute can help you- it is used to define the amount of logging to be performed on the console. The verbosity level is 0 to 10, where 10 is most detailed. Once you set it to 10, you'll see that console output will contain information regarding the tests, methods, and listeners, etc. <suite name="Suite" thread-count="5" verbose="10"> Note* You can specify -1 and this will put TestNG in debug mode. The default level is 0. Alternatively, you can set the verbose level through attribute in "maven-surefire-plugin" in pom.xml, as shown in the image. #testNG #automationTesting #verbose # #testAutomation
Comments
Post a Comment