Chaining Actions with build() & perform()

Combine multiple actions into a single complex sequence using the builder pattern

Concept

In this practice lab, you will learn how to chain multiple actions together into a single, atomic sequence using the Actions class builder pattern.

Instead of calling perform() after every single action, you can:

Chain multiple actions together in one fluent sequence
Execute them all at once with a single perform() call
Create complex user interactions that flow naturally
Reduce test execution time by batching actions

Builder Pattern Fundamentals

The Actions class uses the builder pattern. Each method returns the Actions object itself, allowing you to chain method calls. Only when you call perform() does Selenium actually execute the queued actions in sequence.

❌ Multiple perform() Calls

Less efficient approach:

actions.moveToElement(field1)

.perform();

actions.sendKeys("text")

.perform();

actions.keyDown(Keys.TAB)

.perform();

Each perform() is a separate network call to the browser
Slower execution time
Actions are not atomic (can be interrupted)

✅ Single Chained Sequence

Efficient approach:

actions.moveToElement(field1)

.sendKeys("text")

.keyDown(Keys.TAB)

.perform();

Single network call containing all actions
Faster execution
Atomic sequence (all or nothing)
More readable and maintainable

Understanding build() and perform()

perform()

Builds the action sequence and immediately executes it. This is what you'll use 99% of the time.

actions.click(btn).perform();

build()

Only builds the action sequence without executing it. Rarely used—typically for very advanced scenarios or custom action handling.

Action action = actions.click(btn).build();
action.perform();

Best Practice

Almost always use perform() directly. Only use build() if you need to store the action sequence for later execution or reuse.

Interactive Practice

Imagine a login form where you need to perform a complex action sequence:

Login Form - Chained Actions Demo

Action Log

No actions yet. Interact with the form or click "Simulate Chain"

Interact with the form to see individual actions, or click "Simulate Chain" to see a complete chained sequence!

Manual interaction (student mental model)

If you were doing this manually:

Click on the Username field to focus it.
Type your username (e.g., "testuser").
Press the TAB key to move to the password field.
Type your password.
Press ENTER to submit the form.

Your Selenium code will chain all these actions into a single atomic sequence using the builder pattern.

Java Code Example

ChainingActions.java

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
WebElement username = driver.findElement(By.id("username"));
WebElement password = driver.findElement(By.id("password"));

Actions actions = new Actions(driver);

// Chained action sequence - all executed atomically
actions
    .moveToElement(username)
    .click()
    .sendKeys("testuser")
    .keyDown(Keys.TAB)
    .keyUp(Keys.TAB)
    .sendKeys("mySecurePassword123")
    .keyDown(Keys.ENTER)
    .keyUp(Keys.ENTER)
    .perform();

driver.quit();

Code Breakdown

actions.moveToElement(username): Moves the mouse to the center of the username field. This is the first action in the chain.
.click(): Clicks on the username field to give it focus. Notice no perform() yet—we're still building the chain.
.sendKeys("testuser"): Types the username into the now-focused field. Still chaining.
.keyDown(Keys.TAB).keyUp(Keys.TAB): Presses and releases the TAB key to move focus to the password field. Using keyDown/keyUp gives you precise control over key events.
.sendKeys("mySecurePassword123"): Types the password into the password field (which is now focused thanks to the TAB key).
.keyDown(Keys.ENTER).keyUp(Keys.ENTER): Presses and releases the ENTER key to submit the form.
.perform();: Finally, this executes the entire chain of actions as a single atomic sequence. All the previous actions are queued until this point.
driver.quit();: Closes the browser after the chained actions complete.

Pro Tip

Single perform() for Related Actions

Group logically related actions into a single chain with one perform(). This makes your tests faster, more atomic, and easier to read.

Readable Formatting

Format your chained actions with each action on its own line. This makes it easy to see the sequence of user interactions at a glance, like reading a script.

Don't Over-Chain

While chaining is powerful, don't chain unrelated actions together. If you need to verify state between actions, use separate chains with assertions in between.

Concept

In this practice lab, you will learn how to chain multiple actions together into a single, atomic sequence using the Actions class builder pattern.

Instead of calling perform() after every single action, you can:

Chain multiple actions together in one fluent sequence

Execute them all at once with a single perform() call

Create complex user interactions that flow naturally

Reduce test execution time by batching actions

Builder Pattern Fundamentals

❌ Multiple perform() Calls

Less efficient approach:

actions.moveToElement(field1)

.perform();

actions.sendKeys("text")

.perform();

actions.keyDown(Keys.TAB)

.perform();

Each perform() is a separate network call to the browser
Slower execution time
Actions are not atomic (can be interrupted)

✅ Single Chained Sequence

Efficient approach:

actions.moveToElement(field1)

.sendKeys("text")

.keyDown(Keys.TAB)

.perform();

Single network call containing all actions
Faster execution
Atomic sequence (all or nothing)
More readable and maintainable

Understanding build() and perform()

perform()

Builds the action sequence and immediately executes it. This is what you'll use 99% of the time.

actions.click(btn).perform();

build()

Only builds the action sequence without executing it. Rarely used—typically for very advanced scenarios or custom action handling.

Action action = actions.click(btn).build();
action.perform();

Best Practice

Almost always use perform() directly. Only use build() if you need to store the action sequence for later execution or reuse.

Interactive Practice

Imagine a login form where you need to perform a complex action sequence:

Login Form - Chained Actions Demo

Action Log

No actions yet. Interact with the form or click "Simulate Chain"

Interact with the form to see individual actions, or click "Simulate Chain" to see a complete chained sequence!

Manual interaction (student mental model)

If you were doing this manually:

Click on the Username field to focus it.
Type your username (e.g., "testuser").
Press the TAB key to move to the password field.
Type your password.
Press ENTER to submit the form.

Your Selenium code will chain all these actions into a single atomic sequence using the builder pattern.

Java Code Example

ChainingActions.java

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
WebElement username = driver.findElement(By.id("username"));
WebElement password = driver.findElement(By.id("password"));

Actions actions = new Actions(driver);

// Chained action sequence - all executed atomically
actions
    .moveToElement(username)
    .click()
    .sendKeys("testuser")
    .keyDown(Keys.TAB)
    .keyUp(Keys.TAB)
    .sendKeys("mySecurePassword123")
    .keyDown(Keys.ENTER)
    .keyUp(Keys.ENTER)
    .perform();

driver.quit();

Code Breakdown

actions.moveToElement(username): Moves the mouse to the center of the username field. This is the first action in the chain.
.click(): Clicks on the username field to give it focus. Notice no perform() yet—we're still building the chain.
.sendKeys("testuser"): Types the username into the now-focused field. Still chaining.
.keyDown(Keys.TAB).keyUp(Keys.TAB): Presses and releases the TAB key to move focus to the password field. Using keyDown/keyUp gives you precise control over key events.
.sendKeys("mySecurePassword123"): Types the password into the password field (which is now focused thanks to the TAB key).
.keyDown(Keys.ENTER).keyUp(Keys.ENTER): Presses and releases the ENTER key to submit the form.
.perform();: Finally, this executes the entire chain of actions as a single atomic sequence. All the previous actions are queued until this point.
driver.quit();: Closes the browser after the chained actions complete.

Pro Tip

Single perform() for Related Actions

Group logically related actions into a single chain with one perform(). This makes your tests faster, more atomic, and easier to read.

Readable Formatting

Format your chained actions with each action on its own line. This makes it easy to see the sequence of user interactions at a glance, like reading a script.

Don't Over-Chain

While chaining is powerful, don't chain unrelated actions together. If you need to verify state between actions, use separate chains with assertions in between.