scrapy-playwright
🎠Playwright integration for Scrapy
Runssource: GitHubhomepagePythonBSD-3-Clausecommit d99f38d34831
Python, BSD-3-Clause licensed. The project labels itself: chrome headless, firefox headless, hacktoberfest, headless browser, javascript renderer, playwright, playwright python and python.
scrapy-playwright runs. An Argusic agent installed it in 2.5 minutes and hit 4 errors on a clean machine with no GPU, and the whole session was recorded.
scrapy-playwright 0.0.48 is installed with Scrapy 2.20 and Playwright 1.65; Chromium browser launched and renders pages through the Scrapy download handler; 47 Chromium tests and 29 unit tests pass. Firefox and Webkit browsers not installed, remote-browser tests need unavailable external processes.
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 93.5 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.
- test_extensions.py: Playwright 1.65 changed PlaywrightContextManager internal API from _connection to _client2 minutes
- test_page_methods.py: get_mimetype() failed because 'file' command not available1 minute
- test_utils.py: w3lib now maps gb2312 to gbk instead of gb180301 minute
- test_browser.py tests hang: need external browser server processes (chromium with --remote-debugging-port, node browser server)
- Install time
- 3 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 4 hit, 3 fixed with no human help
- How the result was proved
- pytest --reactor=asyncio tests/tests_asyncio/ --ignore=tests/tests_asyncio/test_browser.py -k 'Chromium or TestPageMethods or TestSettings' returned 47 passed, 0 failed; a Scrapy spider using the Playwright handler fetched httpbin.org/get via Chromium and returned status 200 with 'playwright' flag
- Model tokens used
- 196,045
- Exact commit tested
- d99f38d34831
- 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.
tests/tests_asyncio/test_settings.py::TestSettings::test_max_contexts PASSED [ 95%] tests/tests_asyncio/test_settings.py::TestSettings::test_max_pages_per_context PASSED [ 97%] tests/tests_asyncio/test_settings.py::TestSettings::test_settings_timeout_value PASSED [100%] tests/tests_asyncio/test_browser_contexts.py: 7 warnings tests/tests_asyncio/test_headers.py: 1 warning tests/tests_asyncio/test_page_methods.py: 6 warnings tests/tests_asyncio/test_playwright_requests.py: 20 warnings All 47 Chromium tests pass (0 failures), all 29 unit tests pass. 2026-11-15T03:35:49.143264Z ERROR codex_core::session: failed to record rollout items: thread 01a1d… tokens used 196,045 All 47 Chromium tests pass (0 failures), all 29 unit tests pass.
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 2.5 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed BSD-3-Clause, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Hit 4 errors during setup, 1 of which were not solved.
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 2.5 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 95.00 | 0.04 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.23 |
Topics (from GitHub)
chrome-headlessfirefox-headlesshacktoberfestheadless-browserjavascript-rendererplaywrightplaywright-pythonpythonpython-asynciopython3scrapywebkit-headless
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/scrapy-playwright)Questions
- Does scrapy-playwright run?
- Yes. scrapy-playwright runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test scrapy-playwright?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d99f38d34831. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test scrapy-playwright?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does scrapy-playwright take to install?
- 2.5 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 scrapy-playwright need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing scrapy-playwright?
- 4 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.
- Where is the evidence for scrapy-playwright?
- 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.