playwright-java
AGENTS.md1.6k starsChanged 25 days agoApache-2.0View on GitHub
The Java client is a port of the JavaScript client in ../playwright/packages/playwright-core/src/client/. When implementing or changing a method, read the corresponding JS file first and mirror its logic. Project checkouts (including the upstream playwright repo) live in the parent directory (../). Use the gh cli to interact with GitHub. The tests are in playwright/src/test/java/com/microsoft/playwright/. A test is a @PlaywrightTest method that takes the fixtures it needs as parameters, resolved by type: Page page, BrowserContext context, Browser browser, BrowserType browserType, Playwright…
- Commits and pushes
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Who's talking about microsoft/playwright-java
- microsoft/playwright“[Feature] Support for Raspberry PI”GitHub · Jan 12, 2021 · 34 reactions
- microsoft/playwright“[Feature] Driver - allow to install only selected browsers”GitHub · Sep 13, 2020 · 14 reactions
- Stack Overflow“Executing Puppeteer using Java”Stack Overflow · Nov 27, 2020 · 10 votes
- microsoft/playwright“[Feature]: Sign windows Binaries and browser exe's”GitHub · Mar 12, 2025 · 4 reactions
- Stack Overflow“Unable to download with playwright headless true from url link”Stack Overflow · Mar 30, 2023 · 4 votes
The biggest 5 of 56 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 56
Talked about on GitHub and Stack Overflow (56 times).
On GitHub · 50
- Jan 12, 2021[Feature] Support for Raspberry PI — microsoft/playwright34 reactions · 8 comments
- Sep 13, 2020[Feature] Driver - allow to install only selected browsers — microsoft/playwright14 reactions · 3 comments
- Mar 12, 2025[Feature]: Sign windows Binaries and browser exe's — microsoft/playwright4 reactions · 8 comments
- Apr 2, 2023explore adding first-class support for playwright — karatelabs/karate3 reactions · 31 comments
- Jul 15, 2026[Feature]: Support order-insensitive array matching in toHaveText — microsoft/playwright2 reactions · 2 comments
45 more on GitHub
- Jan 20, 2025Attempt 1 failed: BrowserType.launch: ENOSPC: no space left on device, mkdtemp '/tmp/playwright-artifacts-aNE1l9' — ScrapeGraphAI/Scrapegraph-ai1 reaction · 2 comments
- Sep 30, 2023JUnit codegen — microsoft/playwright1 reaction · 7 comments
- May 24, 2023Updated documentation URLs to use Playwright Homepage — microsoft/playwright1 reaction
- May 18, 2021fix: compute payload mime type on server — microsoft/playwright1 reaction
- Nov 7, 2026chore(deps): bump com.microsoft.playwright:playwright from 1.63.0 to 1.64.0 — anandbagmar/teswiz0 reactions
- Nov 6, 2026chore: bump com.microsoft.playwright:playwright from 1.62.0 to 1.64.0 — pmodv/WebGoat0 reactions
- Nov 5, 2026chore: bump com.microsoft.playwright:playwright from 1.62.0 to 1.64.0 — JoFloresGutierrez06/Actividad-12-ciber0 reactions · 1 comment
- Nov 5, 2026chore: bump com.microsoft.playwright:playwright from 1.62.0 to 1.64.0 — Jcmalanco/Actividad-12-ciber0 reactions
- Nov 3, 2026Bump com.microsoft.playwright:playwright from 1.58.0 to 1.64.0 in /backend — RakshitRao2712/Heimdall0 reactions
- Nov 2, 2026chore: bump com.microsoft.playwright:playwright from 1.62.0 to 1.64.0 — WebGoat/WebGoat0 reactions
- Nov 2, 2026Bump com.microsoft.playwright:playwright from 1.60.0 to 1.64.0 — Aldaviva/playwright-extra-install-arguments0 reactions
- Nov 2, 2026build(deps-dev): bump com.microsoft.playwright:playwright from 1.62.0 to 1.64.0 — lordlamer/jknowledgeroot0 reactions · 1 comment
- Nov 1, 2026chore(deps): bump com.microsoft.playwright:playwright from 1.62.0 to 1.64.0 — bohdankordon/vulcan-schedule-monitor0 reactions
- Nov 1, 2026Bump com.microsoft.playwright:playwright from 1.61.0 to 1.64.0 — earlbertmercado/playwright-saucedemo-java0 reactions
- Oct 31, 2026build: bump com.microsoft.playwright:playwright from 1.63.0 to 1.64.0 — samueleniccolai-dev/gerio-lab0 reactions
- Oct 31, 2026chore(deps-dev): bump com.microsoft.playwright:playwright from 1.63.0 to 1.64.0 — RsheedAlo/medtech-qa-showcase0 reactions
- Oct 31, 2026chore(deps-dev): bump com.microsoft.playwright:playwright from 1.63.0 to 1.64.0 in /api — araujovito/atlas-cientifico0 reactions
- Oct 30, 2026Bump com.microsoft.playwright:playwright from 1.63.0 to 1.64.0 in /java-app — gj-boltron/github-actions-demo0 reactions
- Oct 30, 2026chore(deps): bump com.microsoft.playwright:playwright from 1.63.0 to 1.64.0 — kestra-io/plugin-playwright0 reactions · 3 comments
- Oct 30, 2026chore(deps): bump com.microsoft.playwright:playwright from 1.62.0 to 1.64.0 — iida-27z/java-env-tmp0 reactions · 1 comment
- Oct 30, 2026Bump com.microsoft.playwright:playwright from 1.62.0 to 1.64.0 — yeshallbeasgods/refined-joyous-camellia0 reactions
- Oct 29, 2026chore(deps): bump com.microsoft.playwright:playwright from 1.62.0 to 1.64.0 — thiyagarajan2002/ai-testing-agent-v30 reactions
- Oct 28, 2026chore: bump com.microsoft.playwright:playwright from 1.62.0 to 1.64.0 — Hajarelb/workshop3-G20 reactions
- Oct 28, 2026chore(deps): bump com.microsoft.playwright:playwright from 1.47.0 to 1.64.0 — huawei-zxs/kestra0 reactions · 1 comment
- Oct 28, 2026chore: bump com.microsoft.playwright:playwright from 1.62.0 to 1.64.0 — darrylsarkisian-debug/acme-webgoat0 reactions
- Oct 28, 2026build(deps): bump com.microsoft.playwright:playwright from 1.61.0 to 1.64.0 — XSU15/kestra0 reactions · 1 comment
- Oct 27, 2026build(deps): bump com.microsoft.playwright:playwright from 1.61.0 to 1.64.0 — AiSecurityServices/kestra0 reactions · 1 comment
- Oct 27, 2026chore: bump com.microsoft.playwright:playwright from 1.62.0 to 1.64.0 — sbshivam10/WebGoatFresh0 reactions
- Oct 27, 2026chore(deps): bump com.microsoft.playwright:playwright from 1.63.0 to 1.64.0 — Mariyo/ktor-template0 reactions
- Oct 27, 2026chore(deps): Bump com.microsoft.playwright:playwright from 1.62.0 to 1.64.0 — conciso/keycloak-extensions0 reactions · 1 comment
- Oct 26, 2026Bump com.microsoft.playwright:playwright from 1.62.0 to 1.64.0 — silvaemy/WebGoat-Testing0 reactions
- Oct 26, 2026Bump com.microsoft.playwright:playwright from 1.63.0 to 1.64.0 — quarkus-qe/quarkus-startstop0 reactions
- Oct 26, 2026Bump com.microsoft.playwright:playwright from 1.62.0 to 1.64.0 — patrickf314/ui-test-components0 reactions
- Oct 26, 2026Bump com.microsoft.playwright:playwright from 1.63.0 to 1.64.0 in /quarkus-workshop-super-heroes — quarkusio/quarkus-workshops0 reactions · 1 comment
- Oct 26, 2026chore(deps): bump com.microsoft.playwright:playwright from 1.62.0 to 1.64.0 — RafeArnold/the-mind0 reactions
- Oct 26, 2026Bump com.microsoft.playwright:playwright from 1.55.0 to 1.64.0 — JesseEmerson7/issue-tracker0 reactions
- Oct 26, 2026Bump com.microsoft.playwright:playwright from 1.63.0 to 1.64.0 — kihdev/playwright-stealth-4j0 reactions
- Oct 26, 2026Bump com.microsoft.playwright:playwright from 1.63.0 to 1.64.0 — martinelli-workshops/sdd-lab0 reactions
- Oct 26, 2026Bump com.microsoft.playwright:playwright from 1.63.0 to 1.64.0 in /playwright/java — bonigarcia/browser-automation-apis0 reactions
- Oct 26, 2026chore(deps-dev): bump com.microsoft.playwright:playwright from 1.63.0 to 1.64.0 in /backend — Everything-is-Code/migration-toolkit-rhcl0 reactions
- Oct 26, 2026Bump com.microsoft.playwright:playwright from 1.62.0 to 1.64.0 — kompars/webpush0 reactions
- Oct 26, 2026Bump com.microsoft.playwright:playwright from 1.63.0 to 1.64.0 — simasch/hrs0 reactions
- Oct 26, 2026Bump com.microsoft.playwright:playwright from 1.63.0 to 1.64.0 — martinelli-workshops/alpenfeld-portal0 reactions
- Oct 26, 2026Bump com.microsoft.playwright:playwright from 1.63.0 to 1.64.0 in the playwright group across 1 directory — StitchMl/authenticated-media-stream-analyzer0 reactions · 1 comment
- Oct 25, 2026Bump com.microsoft.playwright:playwright from 1.61.0 to 1.64.0 in /packages/java — virtualfanc/slybrowser0 reactions
On Stack Overflow · 6
- Nov 27, 2020Executing Puppeteer using Java10 votes
- Mar 30, 2023Unable to download with playwright headless true from url link4 votes
- Mar 7, 2023com.microsoft.playwright.PlaywrightException: Host system is missing dependencies to run browsers1 vote
- Jun 14, 2023playwright-java inside Docker RuntimeException: Failed to create driver0 votes · 2 answers
- Nov 13, 2022Java Playwright get response body of redirect0 votes · 1 answer
1 more on Stack Overflow
- Feb 21, 2021Gson Failing to call custom Serializer0 votes
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository4 other files it gives its agents.
- playwright/src/test/AGENTS.mdAGENTS.md
- playwright-java-releaseSkill
- playwright-rollSkill
- playwright-triageSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 62
Never add Co-Authored-By agents in commit message.
- Very specific: line 63
Never add "Generated with" in commit message.
- Very specific: line 64
Never add test plan to PR description.
- Distinctive: line 67
Never amend commits: Always create a new commit for follow-up changes, even when iterating on an open PR.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Playwright Java
The Java client is a port of the JavaScript client in ../playwright/packages/playwright-core/src/client/. When implementing or changing a method, read the corresponding JS file first and mirror its logic.
Project checkouts (including the upstream playwright repo) live in the parent directory (../). Use the gh cli to interact with GitHub.
Build and test
scripts/download_driver.sh # the driver, once per DRIVER_VERSION
mvn -B install -D skipTests --no-transfer-progress # build and install every module
mvn exec:java -e -D exec.mainClass=com.microsoft.playwright.CLI -D exec.args="install --with-deps" -f playwright/pom.xml --no-transfer-progress
BROWSER=chromium mvn test -f playwright/pom.xml -D test=TestPageScreenshot --no-transfer-progressmvn test -f playwright/pom.xmlcompiles theplaywrightmodule and its tests, so a change inplaywright/src/main/needs no separate build step. After a change indriver/ordriver-bundle/, runmvn -B install -D skipTests --no-transfer-progress -f <module>/pom.xmlfirst: theplaywrightmodule takes those modules from the local Maven repository.- The project targets Java 8. CI builds with JDK 8 (Zulu) and JDK 25. Do not use a newer language feature or library API.
- There is no lint or format check. The style is the Google Java Style with a two-space indent, and without comments. When you change a file under
playwright/src/test/java/com/microsoft/playwright/tests/, runpython3 scripts/check_test_registry.py. -D test=<Class>runs one class,-D test=<Class>#<method>one method.BROWSERis a comma-separated list ofchromium,firefoxandwebkit; unset, it runs all three.HEADED=1runs headed. A filter that matches no test passes withTests run: 0, so check the count. Each test method has a 120 second timeout, set in the rootpom.xml. Do not setPW_MAX_RETRIES, which reruns a failed test; CI sets it to 3. The reports are inplaywright/target/surefire-reports/.
Tests
The tests are in playwright/src/test/java/com/microsoft/playwright/. A test is a @PlaywrightTest method that takes the fixtures it needs as parameters, resolved by type: Page page, BrowserContext context, Browser browser, BrowserType browserType, Playwright playwright, BrowserName browserName, Server server, HttpsServer httpsServer and @TempDir Path. The method runs once per selected browser, with a context and a page of its own; the browser and the servers are shared. A class overrides options with @Fixture methods, and skips a browser with @DisabledOnBrowser or @EnabledOnBrowser. Drive the page with page.setContent(...) or page.navigate(server.PREFIX + "/..."), and the server with server.setRoute(...), server.setRedirect(...), server.futureRequest(...) and server.EMPTY_PAGE.
| Directory | Use for |
com/microsoft/playwright/ | the Java-only tests, one class per feature (TestPageScreenshot, TestBrowserContextHar). A regression test for a bug of the Java client goes here, in the class that owns the feature, as one added case. |
com/microsoft/playwright/tests/page/, tests/library/ | line-by-line ports of upstream tests/page and tests/library, one class per spec file (TestPageCheck for page-check.spec.ts), each test titled @DisplayName("CH-001 ...") with the upstream identifier. Do not add a test or an assertion that upstream does not have. When the port that covers a bug carries @Fixme("java: ..."), the fix removes the mark, and that port is the regression test. playwright/src/test/AGENTS.md has the rules. |
com/microsoft/playwright/junit/ | the public JUnit extension, @UsePlaywright |
Tag a regression test with the issue as the Java-only tests do: a comment with the full URL on the first line of the test body, // https://github.com/microsoft/playwright-java/issues/<n>. Good models: TestBrowserContextExposeFunction, shouldNotDispatchBindingOnAClosedPage (a binding, a popup and a context of its own in a try-with-resources block); TestTracing, shouldRecoverTracingAfterAFailedStop (a tagged test with @TempDir on context.tracing()).
Commit Convention
Semantic commit messages: label(scope): description
Labels: fix, feat, chore, docs, test, devops
git checkout -b fix-39562
# ... make changes ...
git add <changed-files>
git commit -m "$(cat <<'EOF'
fix(proxy): handle SOCKS proxy authentication
Fixes: https://github.com/microsoft/playwright-java/issues/39562
EOF
)"
# **Never `git push` without an explicit instruction to push.**
git push origin fix-39562
gh pr create --repo microsoft/playwright-java --head <user>:fix-39562 \
--title "fix(proxy): handle SOCKS proxy authentication" \
--body "$(cat <<'EOF'
## Summary
- <describe the change very! briefly>
Fixes https://github.com/microsoft/playwright-java/issues/39562
EOF
)"Never add Co-Authored-By agents in commit message.
Never add "Generated with" in commit message.
Never add test plan to PR description. Keep PR description short — a few bullet points at most.
Branch naming for issue fixes: fix-<issue-number>.
Never amend commits. Always create a new commit for follow-up changes, even when iterating on an open PR. Amending rewrites history and forces a force-push, losing the incremental review trail. Only amend if the user explicitly says so.
Never git push without an explicit instruction to push. Applies even when a PR is already open for the branch — additional commits are immediately visible to reviewers. Commit locally, report what was committed, and wait. Only push when the user's message contains "push", "upload", "create PR", "ship it", or equivalent.
Skills
- playwright-roll (
.claude/skills/playwright-roll/SKILL.md) — roll Playwright Java to a new upstream version: bump the driver, regenerate the API, and port relevant upstream changes. - playwright-java-release (
.claude/skills/playwright-java-release/SKILL.md) — prepare a release after the rolling PR merges: cut the release branch, mark the Maven version, and draft the GitHub release. - playwright-cherry-pick (upstream,
../playwright/.claude/skills/playwright-cherry-pick/SKILL.md) — cherry-pick a merged PR into arelease-1.Xbranch ascherry-pick(#<pr>): <original title>. Use the same rules for this repo's release branches.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

