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
What is an ARIA Snapshot in Playwright? An ARIA snapshot in Playwright is a structured representation of a page’s accessibility tree , which is used by assistive technologies (e.g., screen readers) to interpret the content of a web page. This snapshot helps verify if elements have the correct roles, names, and properties required for accessibility. Playwright provides the page.accessibility.snapshot() API to capture this accessibility tree at any given moment during test execution. How Does ARIA Work? ARIA ( Accessible Rich Internet Applications ) is a set of attributes that help improve accessibility by defining roles, states, and properties for elements that are not natively accessible. Example: In this case, the aria-label ensures that screen readers identify the button as “Submit Form.” How to Use ARIA Snapshots in Playwright? Playwright’s accessibility.snapshot() method retrieves the accessible structure of the page. Ex...
Comments
Post a Comment