To contribute to pytest-selenium you can use Pipenv to manage a python virtual environment and pre-commit to help you with styling and formatting.

To setup the virtual environment and pre-commit, run:

$ pipenv install --dev
$ pipenv run pre-commit install

If you’re not using Pipenv, to install pre-commit, run:

$ pip install pre-commit
$ pre-commit install

Automated Testing

All pull requests and merges are tested in Travis CI based on the .travis.yml file.

Usually, a link to your specific travis build appears in pull requests, but if not, you can find it on the pull requests page

The only way to trigger Travis CI to run again for a pull request, is to submit another change to the pull branch.

You can do this with git commit –allow-empty

Running Tests

You will need Tox installed to run the tests against the supported Python versions. If you’re using Pipenv it will be installed for you.

With Pipenv, run:

$ pipenv run tox

Otherwise, to install and run, do:

$ pip install tox
$ tox


To run the tests you’re going to need some browser drivers.


To install the latest chromedriver on your Mac or Linux (64-bit), run:

$ ./installation/

For Windows users, please see here.


To install the latest geckodriver on your Mac or Linux (64-bit), run:

$ ./installation/


Instructions for safaridriver.


Instructions for edgedriver.


Instructions for iedriver.

Releasing a new version

Follow these steps to release a new version of the project:

  1. Update your local master with the upstream master (git pull --rebase upstream master)
  2. Create a new branch and update news.rst with the new version, today’s date, and all changes/new features
  3. Commit and push the new branch and then create a new pull request
  4. Wait for tests and reviews and then merge the branch
  5. Once merged, update your local master again (git pull --rebase upstream master)
  6. Tag the release with the new release version (git tag v<new tag>)
  7. Push the tag (git push upstream --tags)
  8. Done. You can monitor the progress on Travis