What if you could click a button once in code and have it work perfectly every time in your tests?
Why Action methods in page class in Selenium Python? - Purpose & Use Cases
Imagine testing a website by clicking buttons and filling forms manually every time you want to check if it works.
You have to remember each step and repeat it exactly, over and over.
Manual testing is slow and tiring.
You might miss a step or click the wrong button by mistake.
It's hard to keep track of all actions and repeat them perfectly each time.
Action methods in a page class let you write each user action once, like clicking a button or entering text.
Then you call these methods anytime in your tests, making testing faster and less error-prone.
driver.find_element(By.ID, 'login').click() driver.find_element(By.ID, 'username').send_keys('user')
class LoginPage: def __init__(self, driver): self.driver = driver def click_login(self): self.driver.find_element(By.ID, 'login').click() def enter_username(self, name): self.driver.find_element(By.ID, 'username').send_keys(name)
You can build clear, reusable test steps that save time and reduce mistakes.
Testing a shopping site: instead of repeating clicks to add items to cart, you write an action method once and reuse it in many tests.
Manual testing is slow and error-prone.
Action methods group user steps into reusable code.
This makes tests easier to write, read, and maintain.
Practice
Solution
Step 1: Understand what action methods do
Action methods are designed to perform user-like actions such as clicking buttons or typing text on web elements.Step 2: Identify the role of action methods in page classes
They help keep test code clean by encapsulating these actions inside the page class, making tests easier to read and reuse.Final Answer:
To perform tasks like clicking or typing on web page elements -> Option AQuick Check:
Action methods = perform tasks on elements [OK]
- Confusing action methods with data storage
- Thinking action methods generate reports
- Believing action methods configure browsers
Solution
Step 1: Check method signature and usage of self
Inside a class, methods must have self as the first parameter to access instance variables like driver.Step 2: Verify correct locator usage
Using By.ID with the driver.find_element method is the correct way to locate elements in Selenium Python.Final Answer:
def click_button(self): self.driver.find_element(By.ID, 'btn').click() -> Option DQuick Check:
Method with self and correct locator = def click_button(self): self.driver.find_element(By.ID, 'btn').click() [OK]
- Omitting self parameter in method
- Using find_element without driver or self
- Passing locator as string without By.ID
def click_submit(self):
self.driver.find_element(By.ID, 'submit').click()
return 'Clicked'Solution
Step 1: Understand what happens when element is missing
If the element with ID 'submit' is not found, Selenium raises NoSuchElementException immediately.Step 2: Check method return behavior
The return 'Clicked' only happens after the click succeeds, so it won't be reached if exception occurs.Final Answer:
selenium.common.exceptions.NoSuchElementException will be raised -> Option BQuick Check:
Missing element causes NoSuchElementException [OK]
- Assuming method returns 'Clicked' even if element missing
- Thinking test passes silently without error
- Confusing exception with printed output
def enter_text(self, text):
input_box = self.driver.find_element(By.NAME, 'username')
input_box.sendkeys(text)Solution
Step 1: Check method call spelling
The correct Selenium method to send text is 'send_keys', not 'sendkeys'. This typo causes an AttributeError.Step 2: Verify other parts of the method
The method has self parameter and uses By.NAME correctly, so no changes needed there.Final Answer:
Change 'sendkeys' to 'send_keys' to fix the method call -> Option AQuick Check:
Correct method name is send_keys [OK]
- Misspelling send_keys method
- Changing locator type unnecessarily
- Removing self parameter incorrectly
Solution
Step 1: Understand how to handle dropdowns in Selenium Python
Selenium provides a Select class to handle dropdowns, which must be initialized with the dropdown element.Step 2: Check each option for correct usage
def select_option(self, text): dropdown = Select(self.driver.find_element(By.ID, 'menu')) dropdown.select_by_visible_text(text) correctly creates a Select object and calls select_by_visible_text. def select_option(self, text): dropdown = self.driver.find_element(By.ID, 'menu') dropdown.select_by_visible_text(text) tries to call select_by_visible_text directly on a WebElement, which is invalid. def select_option(self, text): self.driver.find_element(By.ID, 'menu').click() self.driver.find_element(By.XPATH, f'//option[text()="{text}"]').click() manually clicks options but is less clean. def select_option(self, text): self.driver.find_element(By.ID, 'menu').send_keys(text) uses send_keys which may not work reliably.Final Answer:
def select_option(self, text): dropdown = Select(self.driver.find_element(By.ID, 'menu')) dropdown.select_by_visible_text(text) -> Option CQuick Check:
Use Select class for dropdowns [OK]
- Calling select_by_visible_text on WebElement directly
- Not importing or using Select class
- Using send_keys instead of Select for dropdowns
Ready to prove it?
Pass the test and this pattern moves unknown
