Java + Maven
Normal pom.xml project. Clone it, resolve dependencies, and run with Maven.
LOWRY LAB · AUTOMATION STARTER
A deliberately small cross-browser automation starter built with Java 21, Maven, JUnit 5, and Playwright. It already tests the live Creature Forge app, so you start with something working and expand from there.
START HERE
There is no reporting platform, dependency injection container, API framework, workflow layer, or giant configuration system yet. Every abstraction exists because the starter already needs it.
Normal pom.xml project. Clone it, resolve dependencies, and run with Maven.
The test lifecycle stays familiar. BaseTest creates and tears down the browser environment.
Modern locators, auto-waiting, isolated browser contexts, and cross-browser automation.
Chrome, Edge, Firefox, and WebKit for Safari-engine coverage are already selectable from the command line.
ARCHITECTURE
What are we proving?
How do we interact with this screen?
What happens before and after every test?
Which browser runs, and how is it created and cleaned up?
CLONE → CONFIGURE → RUN
java -version
mvn -versionmvn test -DskipTests
mvn exec:java -e \
-Dexec.mainClass=com.microsoft.playwright.CLI \
-Dexec.args="install chromium firefox webkit"mvn testChrome is the default. The test runs against the live Creature Forge architecture demo.
BROWSER TARGETS
mvn test -Dbrowser=chromeInstalled Google Chromemvn test -Dbrowser=edgeInstalled Microsoft Edgemvn test -Dbrowser=firefoxPlaywright Firefoxmvn test -Dbrowser=safariPlaywright WebKit; not installed Safarimvn test -Dbrowser=chrome -Dheadless=falseTHE INCLUDED TEST
The sample test opens Creature Forge, verifies all three architecture options, selects GraphQL, loads the boss example, verifies a GraphQL request appears, and checks that the UI receives Vharos, Warden of the Last Gate.
Open Creature Forge →Creature Forge
↓
Direct REST ✓
REST BFF ✓
GraphQL ✓
↓
Load boss example
↓
Verify returned UI