playwright-go
Playwright for Go a browser automation library to control Chromium, Firefox and WebKit with a single API.
Runssource: GitHubhomepageGoMITcommit 775648cd1805
Go, MIT licensed. The project labels itself: automation, browser automation, chromium, firefox, go, golang, hacktoberfest and headless.
playwright-go runs. An Argusic agent installed it in 11 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Playwright for Go is installed and functional: Playwright driver v1.62.1 launches Chromium 151.0.7922.34 in headless mode, all package tests (0 failures) and all integration test groups (0 failures) pass with real browser interactions including page navigation, DOM queries, locators, assertions, network interception, file uploads, console monitoring, and WebSocket routing.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Go compiler not found in container2 minutes
- Playwright system dependency warning - host missing libgstreamer, libxslt, libsecret, etc.
- TestPageAddLocatorHandlerShouldThrowWhenHandlerTimesOut hangs when running full suite
- Install time
- 11 minutes
- Cold machine to finish
- 42 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- Standalone Go program launched Chromium, created page, navigated to data:text/plain, and all 128+ integration tests passed across 12 separate test groups including TestBrowser (29/29 pass), TestPage (66+ pass), TestElementHandle (28/28 pass), TestLocator (76/76 pass when run individually), TestConsole, TestDialog, TestDownload, TestFrame, TestRoute, TestScreencast, TestWebSocket, TestWorker. Package-level tests all pass (18.6s).
- Model tokens used
- 167,941
- Exact commit tested
- 775648cd1805
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Page group 2: ok github.com/mxschmitt/playwright-go/tests 2.421s Page group 3: ok github.com/mxschmitt/playwright-go/tests 10.582s Now let me run the remaining groups and then produce the final report. exec /bin/sh -lc 'export GOROOT=/home/runner/go-install GOPATH=/home/runner/go PATH="/home/runner/go-ins… succeeded in 5064ms: === Element handle tests === ok github.com/mxschmitt/playwright-go/tests 4.582s All tests pass. Here is the final report: tokens used 167,941 All tests pass. Here is the final report:
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 11 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 5 automation projects Argusic has installed and timed, playwright-go was the 5th fastest to reach a running state, and 4 of 5 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
automationbrowser-automationchromiumfirefoxgogolanghacktoberfestheadlessheadless-chromeplaywrightseleniumwebkit
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/playwright-go)Questions
- Does playwright-go run?
- Yes. playwright-go runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test playwright-go?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 775648cd1805. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test playwright-go?
- The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does playwright-go take to install?
- 11 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does playwright-go need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing playwright-go?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does playwright-go compare with the alternatives?
- Of the 5 automation projects Argusic has installed and timed, playwright-go was the 5th fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for playwright-go?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.