QA Selenium Java Writer

QA Selenium Java Writer

Purpose

Write Selenium Java E2E tests from test case specifications. Transform structured test cases (from qa-testcase-from-docs, qa-manual-test-designer, qa-browser-data-collector, or specs) into executable Selenium Java test files with JUnit 5, Page Object Model, explicit waits, AssertJ assertions, and Allure reporting.

Trigger Phrases

• "Write Selenium Java tests for [feature/flow]"
• "Generate Selenium E2E tests in Java"
• "Create Selenium Java tests with POM"
• "Add Selenium Java tests for [URL/page]"
• "Selenium Java with JUnit 5 and Allure"
• "Selenium Java Page Object Model tests"
• "Headless Selenium Java tests for [feature]"
• "Selenium Java tests with WebDriverWait"
• "Heal my failing Selenium Java tests"

Key Features

Workflow

1. Read test cases — From specs, requirements, manual test designs, or browser-collected data
2. Analyze app — Inspect pages, forms, flows; identify locators and interactions
3. Generate test classes with POM — Produce {Feature}Test.java with Page Objects in pages/
4. Configure WebDriver — Set up driver lifecycle, headless options, timeouts
5. Add Allure annotations — @Step for steps, @Description, @Severity for reporting
6. Run — User runs mvn test or ./gradlew test to execute tests

Context7 MCP

Use Context7 MCP for Selenium Java documentation when:

• WebDriver API or ExpectedConditions syntax is uncertain
• PageFactory, Actions, or Select handling needs verification
• Browser-specific options (Chrome, Firefox headless) require up-to-date reference

Key Patterns

Wait Strategies

Prefer explicit waits; avoid implicit waits for reliability:

WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(10));
WebElement element = wait.until(ExpectedConditions.elementToBeClickable(By.id("submit-btn")));
element.click();

Common expected conditions: visibilityOfElementLocated, elementToBeClickable, presenceOfElementLocated, textToBePresentInElement, urlContains.

File Naming

• {Feature}Test.java — Test classes (e.g., LoginTest.java, CheckoutTest.java)
• pages/{Feature}Page.java — Page objects (e.g., pages/LoginPage.java, pages/CheckoutPage.java)
• Place in src/test/java per Maven/Gradle convention

Scope

Can do (autonomous):

• Generate Selenium Java E2E tests from test case specs
• Apply Page Object Model with PageFactory
• Use explicit waits (WebDriverWait + ExpectedConditions)
• Configure WebDriver (Chrome, Firefox, Edge, headless)
• Use AssertJ for fluent assertions
• Add Allure annotations for reporting
• Configure maven-surefire-plugin for parallel execution
• Use Context7 MCP for Selenium Java docs
• Delegate to qa-test-healer when tests fail (Heal Mode)

Cannot do (requires confirmation):

• Change production code structure
• Add dependencies not in pom.xml/build.gradle
• Override project Selenium/JUnit config without approval
• Navigate to URLs not provided

Will not do (out of scope):

• Execute tests (user runs mvn test)
• Write Playwright/Cypress tests (use qa-playwright-ts-writer, qa-cypress-writer)
• Modify CI/CD pipelines
• Bypass security or access restricted areas

References

• references/patterns.md — POM, waits, selectors, actions, Select, alerts, frames
• references/config.md — Maven/Gradle config, WebDriver setup, parallel execution
• references/best-practices.md — Java Selenium best practices

Quality Checklist

• Explicit waits used; avoid implicit waits where possible
• No Thread.sleep; prefer WebDriverWait + ExpectedConditions
• POM pattern applied with PageFactory
• Stable locators (ID, data attributes, CSS; XPath as fallback)
• Tests independent (no shared state, order-independent)
• Proper teardown (driver.quit in @AfterEach)
• AssertJ used for assertions
• Allure annotations (@Step, @Description, @Severity) where applicable
• Traceability to test case IDs where applicable
• No hardcoded secrets (use env vars)
• File naming follows {Feature}Test.java convention

Troubleshooting