【QA Automation】E2E Testing with Selenium | Automate Member Registration Flow (Python)

“I’m tired of filling out registration forms manually every single time…” — Sound familiar?
In this article, we’ll walk through a script built with Python × Selenium that fully automates
the Yodobashi Camera member registration form — from form input and submission all the way to login verification.
We’ll cover robust element detection using multiple XPath patterns, debug-friendly logging and screenshots,
and the QA automation design philosophy you can apply to real projects right away.

Test Perspectives

This script covers the following test perspectives. As a QA engineer, clearly defining “what this test is guaranteeing” is essential in real-world projects.

What This Script Can Do

A single class handles the full flow from registration to logout to login — a complete, self-contained automation.

Full Automation Flow

The signup_complete() method orchestrates all steps. Each step is an independent method — easy to debug and reuse.

Here’s what it looks like when the script runs — all fields filled in automatically with the test data dictionary. Swapping to different test data is as simple as editing one Python dict.

▲ The registration form after Selenium automation runs — all fields correctly populated with the test data

Full Source Code

from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC
from selenium.webdriver.support.ui import Select
from datetime import datetime
import os
import time

class YodobashiAutoSignup:
    def __init__(self, headless=False):
        self.top_url = "https://www.yodobashi.com/"
        self.register_url = "https://order.yodobashi.com/yc/member/register/index.html"
        options = webdriver.ChromeOptions()
        options.add_argument('--disable-blink-features=AutomationControlled')
        if not headless:
            options.add_argument('--start-maximized')
        else:
            options.add_argument('--headless')
        options.add_argument('--disable-popup-blocking')
        self.driver = webdriver.Chrome(options=options)
        self.wait = WebDriverWait(self.driver, 15)
        self.log_folder = os.path.join(
            os.path.expanduser("~"), "Desktop", "yodobashi_signup_logs"
        )
        self.setup_log_folder()
        self.log_file = os.path.join(
            self.log_folder,
            f"signup_log_{datetime.now().strftime('%Y%m%d_%H%M%S')}.txt"
        )

    def setup_log_folder(self):
        if not os.path.exists(self.log_folder):
            os.makedirs(self.log_folder)

    def log(self, message):
        timestamp = datetime.now().strftime('%Y-%m-%d %H:%M:%S')
        log_message = f"[{timestamp}] {message}"
        print(log_message)
        with open(self.log_file, 'a', encoding='utf-8') as f:
            f.write(log_message + '\n')

    def take_screenshot(self, name):
        screenshot_name = name.replace('(', '_').replace(')', '').replace(' ', '_')
        screenshot_path = os.path.join(
            self.log_folder,
            f"screenshot_{screenshot_name}_{datetime.now().strftime('%H%M%S')}.png"
        )
        self.driver.save_screenshot(screenshot_path)
        self.log(f"  📷 Screenshot: {os.path.basename(screenshot_path)}")
        return screenshot_path

    # ---- Methods: fill_basic_info / fill_address / fill_contact_info /
    #      fill_password / accept_terms / click_next_button /
    #      click_confirm_button / navigate_to_register_page /
    #      signup_complete / login / logout / reset_password / close ----

# Usage Example
if __name__ == "__main__":
    user_data = {
        "last_name": "Yamada",
        "first_name": "Taro",
        "last_kana": "ヤマダ",
        "first_kana": "タロウ",
        "postal_code": "1500001",
        "address_detail": "1-1-1",
        "building": "Sample Building 101",
        "phone": "09012345678",
        "birth_year": "1990",
        "birth_month": "1",
        "birth_day": "1",
        "email": "test822211@example.com"
    }

    bot = YodobashiAutoSignup(headless=False)
    try:
        result = bot.signup_complete(user_data, password="hjerty12")
        print(f"Result: {result['message']}")
    finally:
        bot.close()

Method Breakdown

The class consists of 10+ methods, each with a clear, single responsibility. This makes it easy to debug individual steps, reuse logic, and extend the script for new use cases.

① __init__() — Class Initialization & ChromeDriver Setup

This method runs when the class is instantiated. It configures ChromeDriver options, sets up the log folder, and initializes WebDriverWait. Simply changing headless=False to True hides the browser window — making it ready for CI/CD environments right out of the box.

② log() / take_screenshot() — Logging & Evidence Collection

log() outputs timestamped messages to both the console and a text file simultaneously. take_screenshot() captures the current browser state as a PNG at any point in the flow. With both methods embedded at every step, you can trace exactly which step failed and why — using both visual screenshots and text logs.

③ fill_basic_info() — Name & Furigana Input

All input[type="text"] elements are fetched at once and identified by checking placeholder and name attributes. Rather than simply targeting “the first input on the page,” this attribute-based approach prevents breakage when form order changes.

④ fill_address() — Postal Code Search & Address Input

Address input is a multi-step interaction: postal code search → candidate selection → street address input. The 7-digit postal code is split into first 3 and last 4 digits, entered into two separate inputs, then the “Search Address” button is found via XPath and clicked.

postal = user_data['postal_code']  # e.g. '1500001'
postal1 = postal[:3]   # '150'
postal2 = postal[3:]   # '0001'

# Extract inputs whose name attribute contains 'zip' or 'postal'
postal_inputs = []
for inp in self.driver.find_elements(By.XPATH, "//input[@type='text']"):
    name_attr = inp.get_attribute('name') or ''
    if 'zip' in name_attr.lower() or 'postal' in name_attr.lower():
        postal_inputs.append(inp)

⑤ fill_contact_info() — Phone, Date of Birth & Email

Phone numbers are handled for both 11-digit and 10-digit formats, split into 3 parts. Birth month/day are <select> dropdowns — handled using the Select class with select_by_value().

⑥ accept_terms() — Terms of Service Checkbox

The checkbox is located via its ID, then checked using a 3-tier fallback: normal click → JS click → direct JS property assignment. State is verified with is_selected() afterward.

⑦ click_next_button() / click_confirm_button() — Screen Transition Buttons

Multiple XPath selectors are stored in an array and tried in order. Elements containing “Back” or “Cancel” are explicitly excluded.

⑧ login() / logout() — Login Verification & Cleanup

After registration, the script immediately performs logout → login, verifying not just that registration succeeded but that the account is fully functional end-to-end.

⑨ reset_password() — Password Reset Flow

Automates the “Forgot your password?” flow — entering email, name, then submitting. Enables automated testing of the password reset feature for full login scenario coverage.

Sample Execution Log

Running the script outputs logs like this to both the console and a text file in real time.

[2025-07-10 14:32:01] ======================================================================
[2025-07-10 14:32:01] Yodobashi Camera Member Registration Automation (Full Flow)
[2025-07-10 14:32:01] Password: hjerty12
[2025-07-10 14:32:02] [Step 1] Navigating to member registration page...
[2025-07-10 14:32:05]   ✓ Registration link clicked
[2025-07-10 14:32:08]   📷 Screenshot: screenshot_01_registration_page_143208.png
[2025-07-10 14:32:08] [Step 2] Filling in basic information...
[2025-07-10 14:32:09]   ✓ Last name: Yamada
[2025-07-10 14:32:09]   ✓ First name: Taro
[2025-07-10 14:32:10]   ✓ Last name (Kana): ヤマダ
[2025-07-10 14:32:10]   ✓ First name (Kana): タロウ
[2025-07-10 14:32:11] [Step 3] Filling in address information...
[2025-07-10 14:32:12]   ✓ Postal code: 150-0001
[2025-07-10 14:32:14]   ✓ Address search executed
[2025-07-10 14:32:15]   ✓ Street address: 1-1-1
[2025-07-10 14:32:16] [Step 5] Agreeing to terms...
[2025-07-10 14:32:18]   ✓ Agreed to terms (normal click)
[2025-07-10 14:32:18]   📷 Screenshot: screenshot_02_form_filled_143218.png
[2025-07-10 14:32:19] [Step 6] Proceeding to confirmation screen...
[2025-07-10 14:32:22]   ✓ Click successful
[2025-07-10 14:32:32] ✓ Member registration complete!
[2025-07-10 14:32:45]   ✓ Login successful!
[2025-07-10 14:32:50] Final result: Registration, logout, login, and logout all completed!

======================================================================
Result: Password input failed
Email: test****@example.com
Password: ******
Log file: C:\Users\HP\Desktop\yodobashi_signup_logs\signup_log_****.txt
======================================================================

Here’s what the actual terminal output looks like when the script runs in the author’s environment. Steps 1 through 3 execute in sequence, with each field confirmed by a ✓.

▲ Real terminal output — Step 1 (navigation) → Step 2 (basic info) → Step 3 (address) run in sequence with each field confirmed

Ideas for Taking It Further

Use Cases & Extensions

Applying This to Real Projects: POM × CI/CD

Pitfalls & Lessons Learned

Here are the key issues I encountered during implementation. I hope this helps others who run into the same problems.

① Checkbox Does Not Respond to a Normal Click

Executing click() on the terms checkbox sometimes failed to check it. The cause was that the checkbox itself was hidden with visibility:hidden, and the site was designed to click the label element instead.

# ❌ Normal click may not work
checkbox = driver.find_element(By.ID, "js_i_checkPrivacyPolicyAgreement")
checkbox.click()

# ✅ Solved with a 3-step fallback: click → JS click → direct property change
try:
    checkbox.click()
except:
    driver.execute_script("arguments[0].click();", checkbox)
    if not checkbox.is_selected():
        driver.execute_script("arguments[0].checked = true;", checkbox)

💡 Key Takeaway： arguments[0].click() (firing a click event) and arguments[0].checked = true (directly changing the property) are different. Having both in your toolkit covers nearly every scenario.

② Dropdown (select tag) Cannot Be Selected with a Direct Click

The birth month and day fields were dropdowns, and a regular click() could not select values. I got stuck because I didn’t know that the Select class is required for this.

# ❌ Direct click cannot select a value
month_element.click()

# ✅ Wrap with Select class and operate
from selenium.webdriver.support.ui import Select
select = Select(month_element)
select.select_by_value("1")  # Select January

💡 Key Takeaway： Always use the Select class for <select> tags. Don’t forget to import it.

③ A Single XPath Pattern for Buttons Breaks Easily

I specified the “Next” button with a single XPath pattern, and a minor site change caused it to no longer be found. Button text often has multiple variations such as “Next”, “Proceed”, or “Continue”, so a single pattern is insufficient.

# ❌ A single pattern breaks easily
button = driver.find_element(By.XPATH, "//button[text()='Next']")

# ✅ Fallback design: try multiple patterns in order
selectors = [
    "//button[contains(text(),'Next')]",
    "//input[@type='submit']",
    "//a[contains(text(),'Next')]",
]
for selector in selectors:
    elements = driver.find_elements(By.XPATH, selector)
    if elements:
        elements[0].click()
        break

💡 Key Takeaway： A fallback design that tries multiple selectors in priority order is a best practice for real-world Selenium tests.

④ Locating the Postal Code Field Was Tricky

I was directly specifying the postal code field by id, but a site redesign changed the id and broke the test. I learned that partial matching is more resilient to changes than exact matching.

# ❌ Exact id match is fragile
driver.find_element(By.ID, "zipCode1")

# ✅ Flexible partial match on name attribute
for inp in driver.find_elements(By.XPATH, "//input[@type='text']"):
    name_attr = inp.get_attribute('name') or ''
    if 'zip' in name_attr.lower() or 'postal' in name_attr.lower():
        postal_inputs.append(inp)

💡 Key Takeaway： Partial attribute matching is more resilient to site changes than exact ID or class name matching, reducing long-term maintenance costs.

⑤ Verifying Login Success Was Difficult

I struggled to determine whether login was successful. In some cases the URL didn’t change after login, meaning URL or page title alone wasn’t enough to verify success.

# ❌ URL alone may not be sufficient
if "mypage" in driver.current_url:
    print("Login successful")

# ✅ Verify by checking text in the page body
body_text = driver.find_element(By.TAG_NAME, "body").text
if "Hello" in body_text or "Welcome" in body_text:
    print("Login successful")

⚠️ Note： The text used for verification varies by site. Always check the actual post-login page to identify text that is reliably present.

Summary

In this article, we walked through a script that fully automates the Yodobashi Camera member registration flow using Python × Selenium.

After the script completes, the yodobashi_signup_logs folder on your Desktop contains a log file and timestamped screenshots saved automatically — ready to use as test evidence right away.

▲ Auto-saved log folder contents — log file + 4 screenshots organized with timestamps, ready to use as test evidence

This script was designed with the goal of reaching production-ready automation quality — not just a quick prototype, but something you can actually use and build on in real QA work. Check out the full source code on GitHub and customize it to fit your own project!