pytest-selenium logo

pytest-selenium

Pytest plugin for running Selenium WebDriver tests, providing fixtures for browsers, capabilities and Sauce Labs/BrowserStack integration.

-

Our Verdict

Only pick this if you are stuck on Selenium; new browser tests belong in Playwright or Cypress.

Pros

  • Browser and capabilities fixtures baked in
  • Sauce Labs and BrowserStack integration
  • Good fit for existing pytest suites

Cons

  • Selenium is aging vs Playwright and Cypress
  • Flaky by nature of WebDriver stack
  • Maintenance has slowed significantly
  • pytest-playwright is usually a better choice today
Best for: Legacy Selenium suites migrated into pytest Not for: Greenfield browser testing where Playwright offers far less flakiness

When to Use pytest-selenium

Good fit if you need

  • Browser fixtures with BrowserStack/Sauce Labs integration
  • Selenium WebDriver test execution across browsers in CI
  • Screenshot capture on test failure for debugging
  • Capability-based browser configuration per test session

pytest-selenium Pricing

Pricing Model
free
Free Tier
Yes
Entry Price
β€”
Enterprise Available
No
Transparency Score
β€”

Beta β€” estimates may differ from actual pricing

1,000
1001K10K100K1M

Estimated Monthly Cost

$25

Estimated Annual Cost

$300

Estimates are approximate and may not reflect current pricing. Always check the official pricing page.

Project Health

C

Health Score

354 119
Bus Factor

2

Last Commit

1 months

Release Freq

N/A

Open Issues

16

Issue Response

13d

License

NOASSERTION

Last checked: 2026-04-21

Lock-in Assessment

Low 5/5
Lock-in Score
5/5

πŸ”„ Thinking about migrating off pytest-selenium?

Get an AI-drafted migration plan + a copy-paste email to pytest-selenium support requesting a data export. Pick where you're moving to and tell us your context.

Looking for alternatives to pytest-selenium?

Answer 4 quick questions β€” get an AI-ranked shortlist of tools that match your stack and requirements.

Open AI Tool Finder

Community Discussion

Comments powered by Giscus (GitHub Discussions). You need a GitHub account to comment.