A production-ready Selenium framework. Java 17. JUnit 5 with custom extensions. POM pattern. Maven Surefire + Failsafe split. REST Assured for API testing. AssertJ fluent assertions. Java Faker factories. Allure reporting. GitHub Actions CI. 89 passing UI, API, database, and framework tests. $995.
Already own a kit? Sign in for $895 owner pricing.
Twelve production-grade pieces of a Selenium + Java test automation framework — wired together, documented, and ready to ship.
Drop in a Postgres, MySQL, or MongoDB connection string and pull random rows straight from your real DB — no mocks, no fixtures to maintain. Unicode + apostrophe + locale safety, seeded reproducibility, and an identifier-injection guard on every query. CI-verified against live databases every release.
Type-safe BasePage with find / findVisible / safeClick / typeText / hover / scrollIntoView / waitForUrlContains / selectDropdown / screenshot — Selenium 4 idioms, logged, and retry-safe. Every page object inherits from it. Stop rewriting wait logic.
LoginPage, InventoryPage, CartPage, CheckoutPage — real data-test selectors, fluent return-types for chaining, static By constants. The canonical Java POM pattern, done right.
JUnit 5 Jupiter with DriverExtension, LoginExtension, and ScreenshotOnFailure extensions. Annotations: @WithDriver, @LoggedIn — declarative test setup. Same suite runs local and CI.
REST Assured 5.5 wired alongside Selenium for hybrid UI + API tests. ApiVsUiCartTest compares cart state via REST endpoints against the rendered UI. AllureRestAssured filter logs every request/response into the Allure report.
Maven Surefire runs fast unit/API tests on `mvn test`. Maven Failsafe runs end-to-end browser tests on `mvn verify`. Two phases, two reports, one pom. CI shards by phase for honest fast-feedback.
assertThat(cart.totalItems()).isEqualTo(3) — readable, chainable, IDE-friendly. No more JUnit assertEquals boilerplate. AssertJ 3.26 with extra matchers for collections, strings, and Throwables.
UserFactory, ProductFactory, CheckoutFactory — Java Faker 1.0.2-powered, seedable for repro. Plus JSON-backed canonical fixtures for tests that need exact values.
Every test annotated with @Story, @Severity, and Allure.step() lambdas. Auto-screenshot on failure via ScreenshotOnFailure extension. allure-junit5 + allure-rest-assured wired in. Run `mvn allure:report` for a full HTML report.
No chromedriver or geckodriver pinning. No WebDriverManager dependency. Selenium 4.6+ ships with Selenium Manager — drivers resolve automatically on every machine and every CI runner.
Maven cache, JDK 17 setup, Surefire and Failsafe phases run separately, Allure results uploaded as artifact. Branch protection-ready status checks.
LoginTest, InventoryTest, CheckoutTest, ApiVsUiCartTest, InventoryApiTest — 32 tests run against saucedemo.com. Clone, `mvn verify`, you see a real test suite go green in under a minute.
README plus deep-dive guides in docs/: PAGE_OBJECT_PATTERN, WAITS_AND_FLAKE, FIXTURES, PARALLEL, CI_CD, TROUBLESHOOTING. Every package, helper, and CI step explained.
Real snippets from the kit. Idiomatic Java, fluent return-types, AssertJ.
src/main/java/com/automationframework/pages/LoginPage.javapackage com.automationframework.pages;
import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
public class LoginPage extends BasePage {
private static final By USERNAME = By.cssSelector("[data-test='username']");
private static final By PASSWORD = By.cssSelector("[data-test='password']");
private static final By LOGIN_BTN = By.cssSelector("[data-test='login-button']");
public LoginPage(WebDriver driver) { super(driver); }
public InventoryPage login(String username, String password) {
typeText(USERNAME, username);
typeText(PASSWORD, password);
safeClick(LOGIN_BTN);
return new InventoryPage(driver);
}
}src/test/java/com/automationframework/e2e/CheckoutTest.java@Story("Checkout")
@Severity(SeverityLevel.CRITICAL)
class CheckoutTest extends BaseTest {
@Test
@LoggedIn
void completesCheckoutEndToEnd() {
Checkout checkout = CheckoutFactory.build();
Confirmation confirmation = new InventoryPage(driver)
.addToCart("sauce-labs-backpack")
.goToCart()
.checkout()
.fillInformation(checkout)
.finish();
assertThat(confirmation.isComplete()).isTrue();
}
}.github/workflows/ci.ymlname: CI
on: [push, pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-java@v4
with:
distribution: temurin
java-version: '17'
cache: maven
- run: mvn -B verify -Dbrowser=chrome -Dheadless=true
- uses: actions/upload-artifact@v4
if: always()
with:
name: allure-results
path: target/allure-resultsWhere Selenium Pro Java sits next to building a Maven test project from scratch, other paid kits, and the Cypress / Playwright alternatives.
A blank Maven archetype gives you a pom.xml and an empty test class. This kit gives you the entire production framework AND the CI pipeline AND 89 passing UI, API, database, and framework tests. You start at week 4, not day 1.
Same scope as paid kits priced 2-5x higher. No subscription, no per-seat pricing, no vendor lock-in. One-time $995, lifetime access, instant download.
Pick Selenium if your team is already on Selenium, if you need the W3C WebDriver standard, or if your shop is Java-first and JUnit is the test runner. Cypress Pro and Playwright Pro exist as sibling kits if your tooling points the other way.
Buy the kit when the reusable engineering foundation is the work you need to avoid. Keep building internally when the framework itself is your team’s product or learning goal.
If the kit avoids about 20 engineering hours at a $50/hour loaded cost, it has paid for itself. That threshold excludes future maintenance, design review, CI debugging, documentation, and onboarding time.
Use your own loaded labor cost and expected setup time; this is a decision aid, not a promised saving.Compatibility is stated against the current published package. Connect the kit to your own application, credentials, environments, and data after download.
Release metadata unavailableYour dashboard retains access to the version delivered with your purchase. Reasonable bug-fix and compatibility updates may be released, but no perpetual update cadence or operation of every future third-party dependency is promised.
Compare the profile above with your organization’s pinned runtime, browser, CI, proxy, and security requirements. For an unlisted constraint, ask before checkout rather than discovering it during setup.
Ask a compatibility question →Drop in a connection string and pull random rows straight from your Postgres, MySQL, or MongoDB. Unicode names, apostrophes, NULLs, weird locales — all the production data that breaks mock-based tests gets exercised every run.
src/test/java/CheckoutTests.javaimport framework.services.realdata.RealData;
var db = RealData.postgres(System.getenv("DB_URL"));
db.connect();
// Pull a real customer with a real order from your DB
var customer = db.getRandomRows("customers",
RandomQueryOptions.builder()
.count(1)
.where(Where.eq("tier", "enterprise"))
.seed("checkout-fixture-1") // reproducible across runs
.build()
).get(0);
driver.get("/account/" + customer.get("id"));
assertEquals(customer.get("name"),
driver.findElement(By.cssSelector("[data-test=name]")).getText());Every release runs the kit's full test suite against ephemeral Postgres, MySQL, and MongoDB containers in GitHub Actions. The proof image just below this section is the actual terminal output of that run — no edits, no rebuilds.
Reproducible Java 17 + Selenium 4 validation against saucedemo.com via mvn verify. Current approved CI evidence is shown when available; otherwise the dated archival capture remains labeled.
No. The kit ships with pure GitHub Actions CI — no Selenium Grid, Sauce Labs, or BrowserStack subscription required. The docs/CI_CD.md guide covers how to add a remote grid when you are ready.
Selenium 4.27. Selenium Manager (built into Selenium 4.6+) handles driver downloads automatically — no chromedriver/geckodriver pinning, no WebDriverManager dependency, ever.
JUnit 5 (Jupiter). TestNG is fine, but JUnit 5 is the modern default for new Java projects, and its extension model is cleaner than TestNG listeners. Migration to TestNG is straightforward if your shop requires it.
Maven. pom.xml is included and tested. Gradle conversion is mechanical — same dependencies, same plugin equivalents (surefire-plugin → test task, failsafe-plugin → integrationTest task).
Yes. BasePage uses fluent waits with ExpectedConditions and retry-on-stale patterns. The full pattern is documented in docs/WAITS_AND_FLAKE.md.
Yes. The framework is application-agnostic — point the base URL system property at your local dev server and the same suite runs against it. No coupling to any application framework.
Yes. CI matrix runs on Ubuntu; the framework itself runs on all three OSes. macOS Apple Silicon supported.
Selenium 4 is the W3C WebDriver standard. Pick this kit if your team is already on Selenium, if you need cross-browser coverage across the full browser matrix, or if your shop is Java-first and JUnit is the test runner. Playwright Pro exists as a sibling kit if your tooling points the other way.
Java 17. The pom.xml is configured with --release 17 so it compiles on any JDK 17 or newer (tested with JDK 21).
Yes. Email support for setup questions and reproducible product defects is included with purchase. Response times vary with request volume; the contact form is also available for pre-sales questions.
An 11-page PDF walking through every directory, every pattern, and the exact flow from npx playwright test down to the system under test.