pytest-play distributed as a docker based command line utility shipped with all supported third party plugins installed for (test) automation playing with YAML files.
See https://hub.docker.com/r/davidemoro/pytest-play.
These instructions will cover usage information and for the docker container
In order to run this container you'll need docker installed.
I assume you have in the current folder a test_*.yml file
containing a valid pytest-play syntax
Main usage
docker run -i --rm -v $(pwd):/src davidemoro/pytest-playStandard pytest parameters (see pytest)
docker run -i --rm -v $(pwd):/src davidemoro/pytest-play -x -k "something"Selenium tests (see play_selenium)
docker run -i --rm -v $(pwd):/src davidemoro/pytest-play --splinter-webdriver=remote --splinter-remote-url=http://USERNAME:ACCESS_KEY@hub.browserstack.com:80/wd/hubIf you are using Windows remove $(pwd) with your current path location.
- pytest
- pytest-play with the following pytest-play plugins included
- pytest supported third party plugins
- python3
Included the following pytest plugins and utilities too:
- pytest-bdd
- pytest-html
- pytest-metadata
- pytest-randomly
- pytest-repeat
- pytest-testrail
- BlazeMeter Taurus/bzt for performance test using pytest-play
Any help will be appreciated (suggestions, pull requests, donations, beer, wine, articles).
We use SemVer for versioning. For the versions available, see the tags on this repository.
- Davide Moro - Initial work - blog
See also the list of pytest-play contributors and pytest-play-docker contributors who participated in this project.
The pytest-play project is licensed under the Apache License 2.0 - see the LICENSE file for details.
-
Python and pytest community
-
Andrea Ratto @neg3ntropy - 10 minutes saved for every build thanks to Docker cache