Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

steero

Disclaimer. steero is provided AS IS, without warranty of any kind, express or implied. Use it entirely at your own risk. It launches and controls web browsers and can act on any site you point it at. The authors accept no liability for data loss or corruption, damage to hardware, systems that will not start, business interruption, or any consequential damages. You are responsible for checking what you automate, keeping tested backups, and being authorised to act on the sites and accounts you drive. steero is not certified for regulated, forensic, safety-critical or high-assurance use. See DISCLAIMER.md. The LICENSE (MIT) is the governing text and prevails wherever it and this summary differ.

Typed, async-first Python driver for the stock Chrome and Firefox you already have, over the W3C WebDriver BiDi standard.

  • No patched browsers. One standard protocol drives Chrome, Edge and Firefox. Firefox needs no driver; Chrome and Edge use chromedriver or msedgedriver (downloaded on first use) or, with backend="chromium-bidi", nothing extra.
  • Auto-waiting before every action, with errors that say which check failed.
  • Typed end to end. The protocol layer is generated from the specification.
  • Runs Playwright for Python scripts by changing the import to steero.compat.playwright; pytest-playwright's fixtures and options work too.
  • Emulation: viewport, devices, locale, timezone, geolocation, permissions, colour scheme, offline, proxy; storage state to log in once; API requests that share the browser's cookies.
  • Tracing with a local trace viewer, video, and a script recorder (steero show-trace, steero codegen).
  • Visual comparison (to_have_screenshot) and ARIA snapshots.
  • Async core, sync API, pytest plugin with failure artifacts, self-healing locators, and an MCP server so AI agents can drive Firefox too.
  • Leaves nothing behind. No orphaned browser processes, no leaked profiles.

Install

pip install steero
steero doctor

Example

import asyncio
import steero
from steero import expect

async def main() -> None:
    async with steero.launch("firefox") as browser:
        page = await browser.new_page()
        await page.goto("https://example.com/login")
        await page.get_by_label("User name").fill("ada")
        await page.get_by_role("button", name="Sign in").click()
        await expect(page.get_by_role("status")).to_have_text("Welcome, ada")

asyncio.run(main())

Sync, with pytest:

from steero.sync_api import expect

def test_login(steero_page):
    steero_page.goto("https://example.com/login")
    steero_page.get_by_label("User name").fill("ada")
    steero_page.get_by_role("button", name="Sign in").click()
    expect(steero_page.get_by_role("status")).to_have_text("Welcome, ada")
pytest --steero-browser chrome --steero-browser firefox

Coming from Playwright

Change the import; the rest of the script stays as it is, timeouts in milliseconds included:

from steero.compat.playwright.sync_api import sync_playwright, expect

with sync_playwright() as p:
    browser = p.firefox.launch()          # stock Firefox; p.chromium is Chrome
    page = browser.new_page()
    page.goto("https://example.com")
    expect(page.get_by_role("heading", level=1)).to_have_text("Example Domain")
    browser.close()

pytest-playwright suites run with pytest -p steero.compat.playwright.pytest. Calls steero cannot honour (WebKit, connect_over_cdp ...) raise UnsupportedFeature naming the call. See the migration guide.

Command line

steero smoke https://example.com          # exit 1 on console errors or failed requests
steero install chromedriver               # or chromium-bidi, chrome@155, firefox@esr
steero screenshot https://example.com out.png --full-page
steero pdf https://example.com out.pdf
steero mcp --browser firefox              # MCP server for AI agents
steero doctor                             # browsers, drivers and cache steero finds
steero show-trace trace.zip               # local trace viewer
steero codegen https://example.com        # record actions into a steero script

What is in the box

Area Highlights
Locators get_by_role/label/text/placeholder/test_id, CSS, XPath, chaining, nth, filter; shadow DOM pierced; strict
Actions click, fill, press, type, check, select, hover, drag, file upload; real BiDi input events
Assertions expect(...): text, value, visibility, count, URL, title, class, CSS, accessible name; not_ and not_to_*
Network route() to fulfill, continue or abort; requests, responses and bodies; downloads
Pages events, dialogs, popups, frames, isolated contexts, cookies, PDF, screenshots
Emulation context options (viewport, locale, timezone, geolocation, permissions, colour scheme, offline, proxy ...), steero.devices, storage state, context.request and steero.request
Visual to_have_screenshot baselines, aria_snapshot and to_match_aria_snapshot
Debugging context.tracing and steero show-trace, video (record_video_dir), steero codegen
Playwright steero.compat.playwright.{sync_api,async_api,pytest}; pytest-playwright's options
pytest steero_page and friends; screenshot, HTML and console saved on failure; --tracing, --video, --screenshot
Healing deterministic fingerprint healing, refuses when unsure, --steero-strict-heal
Agents steero mcp: Model Context Protocol server for Chrome and Firefox
Chrome extras steero.chromium: CDP metrics, CPU throttling, JS coverage

Status

1.0.0rc5. 1.0.0rc2 was tested on Windows and Linux with Chrome 155 and Firefox 158, including a 279-test hard-controls suite (ControlLab) on each browser configuration; rc3 added error-page navigation and listener access; rc4 adds Playwright parity (emulation, tracing, video, codegen, visual comparison, the compat layer, Edge); rc5 adds remote and persistent browsers, HAR, WebSocket routing, the clock, element handles and an HTML test report. Some emulation options are Chrome only; see upstream findings. See the policy for versioning, deprecation and supported browsers, and the changelog.

Documentation

The guides live in docs/: getting started, locators, auto-waiting, network, visual comparison, contexts, emulation and API requests, the pytest plugin, self-healing, tracing and video, codegen, the MCP server, migrating from Selenium or Playwright, and an honest comparison.

Learn steero is a 16-lesson course in docs/course/, with runnable examples in examples/course/. A static demo site and the scripts that automate it are in examples/demo/: run python examples/demo/demo_tour.py.

Contributing

Contributions are welcome: see CONTRIBUTING.md, the Code of Conduct and GOVERNANCE.md. Report security problems privately, as described in SECURITY.md.

License

MIT - see LICENSE.

Metadata

Release files for steero 1.0.0rc5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for steero 1.0.0rc5
File Size Uploaded Provenance Actions
steero-1.0.0rc5.tar.gz 377.8 kB Without provenance Details for steero-1.0.0rc5.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for steero 1.0.0rc5
File Interpreter ABI Platform Actions
steero-1.0.0rc5-py3-none-any.whl Python 3 none any Details for steero-1.0.0rc5-py3-none-any.whl

Total release size: 799.3 kB

Release files / steero-1.0.0rc5.tar.gz

Download URL steero-1.0.0rc5.tar.gz
Size 377.8 kB
Tags Source
SHA-256 checksum
How to use checksums
a903430c04a8043c88b58827e8e88839e7d6fb1a5dc8ff27eaa2fa428a3ccee1
BLAKE2b-256 checksum
How to use checksums
6721238080fa7507c30e5ba2d05283f1a77bd8b0be123e89a8f63f6d22594395
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.5

Release files / steero-1.0.0rc5-py3-none-any.whl

Download URL steero-1.0.0rc5-py3-none-any.whl
Size 421.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bcc445ffc4feb5b722c75386b9332cd0a10d0002ac66aa9b79d2b62c5bda96f4
BLAKE2b-256 checksum
How to use checksums
9a2c926d69f61fe293f716551e7596198ad92f330ba9b7827460f7e75464848a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.5

Security for steero 1.0.0rc5

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page