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 25 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Go! v1.22.2 toolchain works, Playwright driver v1.62.1 installed, projects builds with 'go build .', 85 unit tests pass, full integration test suite passes with real Chromium/Firefox/WebKit browser automation.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.27 (measured)
recorded runs
2
last tested
stars
3,549
forks
250
open issues
5
watchers
35
size
33 MB
created
last push

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.

Time lost to each failure while testing playwright-go, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Test suite failed with 'please install the driver (v1.62.1) first' because browsers were not yet downloaded2 minutes
Install time
25 minutes
Cold machine to finish
30 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
go test -v passed 85 unit tests; go test tests/ passed integration suite with real browser launches (355s); go build . compiled with exit 0
Model tokens used
119,779
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.

/bin/sh -lc 'export PATH="/tmp/explore/pkg/usr/lib/go-1.22/bin:$HOME/go/bin:$PATH" && export GOROOT…
 succeeded in 381795ms:
=== Unit tests ===
85
=== Integration tests ===
ok    github.com/mxschmitt/playwright-go/tests  355.200s
=== Build ===
Build: 0
All tests passed comprehensively — 85 unit tests and a full integration test suite via real browser…
tokens used
119,779
All tests passed comprehensively — 85 unit tests and a full integration test suite via real browser…

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 1 error 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.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 25 minutes to install, slower than the median of the 37 comparable projects Argusic has measured.

Of the 38 automation projects Argusic has installed and timed, playwright-go was the 37th fastest to reach a running state, and 25 of 38 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.27
Argusic Runner1/3Runs100.000.14

Topics (from GitHub)

automationbrowser-automationchromiumfirefoxgogolanghacktoberfestheadlessheadless-chromeplaywrightseleniumwebkit

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/playwright-go.svg)](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 25 minutes, hitting 1 error 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. 2 attempts are 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.27: 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?
25 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?
1 thing broke in the recorded run, and 1 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 38 automation projects Argusic has installed and timed, playwright-go was the 37th fastest to reach a running state, and 25 of 38 reached one at all.
Where is the evidence for playwright-go?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion