ByChained and ByAll

Advanced locator strategies for complex or dynamic pages.

Concept

Sometimes simple locators (single By.id, By.cssSelector, etc.) are not enough, especially on complex pages with nested structures or changing attributes. Selenium offers two helper locator classes to combine locators:

ByChained – chain multiple locators (parent → child → grandchild…).
ByAll – match elements that satisfy any of several locators (OR logic).

These are in org.openqa.selenium.support.pagefactory (or org.openqa.selenium.support in newer versions).

ByChained – Parent → Child search

new ByChained(By.id("form-1"), By.tagName("button"))

What it does

Applies locators step-by-step:
1. Find element(s) by By.id("form-1").
2. Inside those results, find descendant(s) by By.tagName("button").
Equivalent to "find the form with id="form-1", then find a button inside it".

When to use it

When you want to scope your search to a specific container:
- Inputs inside a specific form.
- Buttons inside a specific card or modal.
When the same tag/class appears many times, but you only want those under a particular parent.

Best Practice

Think of it like a structured, readable alternative to long CSS/XPath. Helps avoid accidentally matching elements from the wrong section of the page.

ByAll – OR logic between locators

new ByAll(By.id("btn-submit-1"), By.className("cancel-btn"))

What it does

Combines locators using OR logic:
Returns elements that match any of the supplied locators.
Example: Match element with id="btn-submit-1" or any element with class="cancel-btn".

When to use it

When an element's attributes might change across:
- Environments (dev vs test).
- A/B tests or UI variations.
When you want fallback locators:
- Try ID first, but also accept a known class or name.

Best Practice Note

Use carefully: it can return elements from different areas of the page. Often combined with findElements and filtering/inspection in code.

Interactive Practice

Practice Area: Two Forms with Buttons (ByChained & ByAll Demo)

On this practice page, you'll see two simple forms and practice buttons. Use your Selenium scripts to interact with these actual elements!

Form 1 (ID: form-1)

Important attributes:

Form has id="form-1"
Button has id="btn-submit-1"
ByChained targets: form-1 → button

Form 2 (ID: form-2)

Secondary form

Important attributes:

Form has id="form-2"
Cancel button has class="cancel-btn"
ByAll targets: btn-submit-1 OR cancel-btn

Practice Controls (Visual Demo)

Click these buttons to see which elements the locators would target:

How to Practice with Selenium

For ByChained: Use driver.findElement(new ByChained(By.id("form-1"), By.tagName("button"))) to locate the Submit button in Form 1.
For ByAll: Use driver.findElements(new ByAll(By.id("btn-submit-1"), By.className("cancel-btn"))) to locate both the Submit and Cancel buttons.
Try interacting with the input fields using sendKeys() and clicking the buttons using click().
The forms are fully functional—you can type in the fields and click the buttons to see real interactions!

Java Code Example

ByChainedAndByAllDemo.java

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
By chainedLocator = new ByChained(
    By.id("form-1"),
    By.tagName("button")
);

WebElement submitBtn = driver.findElement(chainedLocator);
System.out.println("Found button in Form 1: " + submitBtn.getText());
submitBtn.click();

By allLocator = new ByAll(
    By.id("btn-submit-1"),
    By.className("cancel-btn")
);

List<WebElement> buttons = driver.findElements(allLocator);
System.out.println("Found " + buttons.size() + " buttons matching either criteria.");

for (WebElement button : buttons) {
    System.out.println("Button text: " + button.getText());
}

driver.quit();

Code Breakdown

new ByChained(By.id("form-1"), By.tagName("button")): Creates a chained locator:
Step 1: find the element with id="form-1".
Step 2: inside that element, find button elements.
WebElement submitBtn = driver.findElement(chainedLocator): Uses the chained locator with findElement to get the button inside Form 1.
submitBtn.getText(): Reads the visible text on the button (e.g. "Submit"), useful for logging and verification.
submitBtn.click(): Clicks the Form 1 submit button, just like a user.
new ByAll(By.id("btn-submit-1"), By.className("cancel-btn")): Creates an OR-style locator that matches:
Any element with id="btn-submit-1", or
Any element with class="cancel-btn".
List<WebElement> buttons = driver.findElements(allLocator): Uses findElements to get all elements matching either locator.
for (WebElement button : buttons) { System.out.println("Button text: " + button.getText()); }: Iterates over all matched buttons (e.g. submit + cancel) and prints their text.
driver.quit(): Closes the browser and ends the WebDriver session.

Pro Tip

Use ByChained for scoping

Use ByChained when you want to limit your search to a specific container (form, card, modal). It reduces the chance of hitting the wrong element in a large page.

Use ByAll as fallback

Use ByAll as a fallback strategy when an element might be identified in more than one way (ID in some builds, class or name in others).

Keep it simple first

Stick with simple locators first (id, cssSelector, XPath). Reach for ByChained and ByAll only when you truly need extra flexibility or robustness.

Concept

ByChained – chain multiple locators (parent → child → grandchild…).

ByAll – match elements that satisfy any of several locators (OR logic).

These are in org.openqa.selenium.support.pagefactory (or org.openqa.selenium.support in newer versions).

ByChained – Parent → Child search

new ByChained(By.id("form-1"), By.tagName("button"))

What it does

Applies locators step-by-step:
1. Find element(s) by By.id("form-1").
2. Inside those results, find descendant(s) by By.tagName("button").
Equivalent to "find the form with id="form-1", then find a button inside it".

When to use it

When you want to scope your search to a specific container:
- Inputs inside a specific form.
- Buttons inside a specific card or modal.
When the same tag/class appears many times, but you only want those under a particular parent.

Best Practice

Think of it like a structured, readable alternative to long CSS/XPath. Helps avoid accidentally matching elements from the wrong section of the page.

ByAll – OR logic between locators

new ByAll(By.id("btn-submit-1"), By.className("cancel-btn"))

What it does

Combines locators using OR logic:
Returns elements that match any of the supplied locators.
Example: Match element with id="btn-submit-1" or any element with class="cancel-btn".

When to use it

When an element's attributes might change across:
- Environments (dev vs test).
- A/B tests or UI variations.
When you want fallback locators:
- Try ID first, but also accept a known class or name.

Best Practice Note

Use carefully: it can return elements from different areas of the page. Often combined with findElements and filtering/inspection in code.

Interactive Practice

Practice Area: Two Forms with Buttons (ByChained & ByAll Demo)

On this practice page, you'll see two simple forms and practice buttons. Use your Selenium scripts to interact with these actual elements!

Form 1 (ID: form-1)

Important attributes:

Form has id="form-1"
Button has id="btn-submit-1"
ByChained targets: form-1 → button

Form 2 (ID: form-2)

Secondary form

Important attributes:

Form has id="form-2"
Cancel button has class="cancel-btn"
ByAll targets: btn-submit-1 OR cancel-btn

Practice Controls (Visual Demo)

Click these buttons to see which elements the locators would target:

How to Practice with Selenium

For ByChained: Use driver.findElement(new ByChained(By.id("form-1"), By.tagName("button"))) to locate the Submit button in Form 1.
For ByAll: Use driver.findElements(new ByAll(By.id("btn-submit-1"), By.className("cancel-btn"))) to locate both the Submit and Cancel buttons.
Try interacting with the input fields using sendKeys() and clicking the buttons using click().
The forms are fully functional—you can type in the fields and click the buttons to see real interactions!

Java Code Example

ByChainedAndByAllDemo.java

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
By chainedLocator = new ByChained(
    By.id("form-1"),
    By.tagName("button")
);

WebElement submitBtn = driver.findElement(chainedLocator);
System.out.println("Found button in Form 1: " + submitBtn.getText());
submitBtn.click();

By allLocator = new ByAll(
    By.id("btn-submit-1"),
    By.className("cancel-btn")
);

List<WebElement> buttons = driver.findElements(allLocator);
System.out.println("Found " + buttons.size() + " buttons matching either criteria.");

for (WebElement button : buttons) {
    System.out.println("Button text: " + button.getText());
}

driver.quit();

Code Breakdown

new ByChained(By.id("form-1"), By.tagName("button"))

Creates a chained locator:

Step 1: find the element with id="form-1".
Step 2: inside that element, find button elements.

WebElement submitBtn = driver.findElement(chainedLocator)

Uses the chained locator with findElement to get the button inside Form 1.

submitBtn.getText()

Reads the visible text on the button (e.g. "Submit"), useful for logging and verification.

submitBtn.click()

Clicks the Form 1 submit button, just like a user.

new ByAll(By.id("btn-submit-1"), By.className("cancel-btn"))

Creates an OR-style locator that matches:

Any element with id="btn-submit-1", or
Any element with class="cancel-btn".

List<WebElement> buttons = driver.findElements(allLocator)

Uses findElements to get all elements matching either locator.

for (WebElement button : buttons) { System.out.println("Button text: " + button.getText()); }

Iterates over all matched buttons (e.g. submit + cancel) and prints their text.

driver.quit()

Closes the browser and ends the WebDriver session.

Pro Tip

Use ByChained for scoping

Use ByChained when you want to limit your search to a specific container (form, card, modal). It reduces the chance of hitting the wrong element in a large page.

Use ByAll as fallback

Use ByAll as a fallback strategy when an element might be identified in more than one way (ID in some builds, class or name in others).

Keep it simple first

Stick with simple locators first (id, cssSelector, XPath). Reach for ByChained and ByAll only when you truly need extra flexibility or robustness.