Create step-wise / incremental tests in pytest.

This is the readme for developers. The documentation for users is available here: https://smarie.github.io/python-pytest-steps/

Contributions are welcome ! Simply fork this project on github, commit your contributions, and create pull requests.

Here is a non-exhaustive list of interesting open topics: https://github.com/smarie/python-pytest-steps/issues

This project uses pytest.

pytest -v pytest_steps/tests/

You may need to install requirements for setup beforehand, using

pip install -r ci_tools/requirements-test.txt

This project uses setuptools_scm to synchronise the version number. Therefore the following command should be used for development snapshots as well as official releases:

python setup.py egg_info bdist_wheel rotate -m.whl -k3

You may need to install requirements for setup beforehand, using

pip install -r ci_tools/requirements-setup.txt

This project uses mkdocs to generate its documentation page. Therefore building a local copy of the doc page may be done using:

mkdocs build -f docs/mkdocs.yml

You may need to install requirements for doc beforehand, using

pip install -r ci_tools/requirements-doc.txt

The following commands generate the html test report and the associated badge.

pytest --junitxml=junit.xml -v pytest_steps/tests/
ant -f ci_tools/generate-junit-html.xml
python ci_tools/generate-junit-badge.py

This project is now automatically deployed to PyPI when a tag is created. Anyway, for manual deployment we can use:

twine upload dist/* -r pypitest
twine upload dist/*

Ax explained in github ('get commandline instructions'):

git checkout -b <git_name>-<feature_branch> master
git pull https://github.com/<git_name>/python-pytest-steps.git <feature_branch> --no-commit --ff-only

if the second step does not work, do a normal auto-merge (do not use rebase!):

git pull https://github.com/<git_name>/python-pytest-steps.git <feature_branch> --no-commit

Finally review the changes, possibly perform some modifications, and commit.