helium

Lighter web automation with Python

Runssource: GitHubPythonMITcommit 624f729746f7

Python, MIT licensed. The project labels itself: chrome, firefox, helium, python, python3, selenium, selenium python and web automation.

helium runs. An Argusic agent installed it in 3 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Helium 7.0.3 installs in a venv and its full 332-test suite passes against a real headless Chrome 157 downloaded by Selenium Manager, with date-input and subprocess tests fixed for this environment.

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.12 (measured)
recorded runs
2
last tested
stars
8,338
forks
511
open issues
55
watchers
83
size
41 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 helium, 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.

  • Chrome session not created: Chrome instance exited when started via helium.start_chrome in container1 minute
  • test_write_into_input_type_date failed: writing '23.08.2024' into <input type=date> with lang=de-DE produced empty value in Chrome 1571 minute
  • test_kill_service_at_exit failed: subprocess python -m api.test_kill_service_at_exit_chrome raised ModuleNotFoundError: No module named 'api'1 minute
Install time
3 minutes
Cold machine to finish
15 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
python -m unittest discover tests -q exited 0: Ran 332 tests in 66.6s, OK; plus start_chrome('https://example.com', headless=True) printed 'Example Domain' title and kill_browser() succeeded
Model tokens used
584,690
Exact commit tested
624f729746f7
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.

- Verified: `python -m unittest discover tests -q` → `Ran 332 tests in 66.6s / OK` (exit 0). Smoke-…
tokens used
584,690
Everything is complete. Here is my report:
**Work done:**
- Read README/docs; installed the package into a fresh venv (`pip install -r requirements/base.txt`…
- No system browser existed, but Selenium Manager auto-downloaded Chrome 157.0.8103.38 + matching c…
- 3 errors encountered and fixed:
  1. **Chrome failed to start via Helium** (`session not created: Chrome instance exited`) — Helium…
  2. **Date-input test failed** — Chrome 157's date input shadow DOM ignores `lang=de-DE`; `23.08.2…
  3. **Subprocess test failed with `ModuleNotFoundError: No module named 'api'`** — fixed `tests/ap…
- Verified: `python -m unittest discover tests -q` → `Ran 332 tests in 66.6s / OK` (exit 0). Smoke-…

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.
  • Installed in 3 minutes, faster than the median of the 3 comparable projects Argusic has measured.
  • 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.
  • Measured 2 times, so the result is not a one-off.

Of the 4 chrome projects Argusic has installed and timed, helium was the 2nd fastest to reach a running state, and 4 of 4 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.
  • A quick evaluation: it was running 3 minutes after the clone.

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.12
Argusic Runner1/3Runs100.000.15

Topics (from GitHub)

chromefirefoxheliumpythonpython3seleniumselenium-pythonweb-automationweb-scrapingwebdriver

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/helium.svg)](https://argusic.com/subject/helium)

Questions

Does helium run?
Yes. helium runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test helium?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 624f729746f7. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test helium?
The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does helium take to install?
3 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 helium need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing helium?
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 helium compare with the alternatives?
Of the 4 chrome projects Argusic has installed and timed, helium was the 2nd fastest to reach a running state, and 4 of 4 reached one at all.
Where is the evidence for helium?
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