Store data created during your pytest
tests execution, and retrieve it at the end of the session, e.g. for applicative benchmarking purposes.
This is the readme for developers. The documentation for users is available here: https://smarie.github.io/python-pytest-harvest/
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-harvest/issues
This project uses pytest
.
pytest -v pytest_harvest/tests/
You may need to install requirements for setup beforehand, using
pip install -r ci_tools/requirements-pip.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-pip.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-pip.txt
The following commands generate the html test report and the associated badge.
pytest --junitxml=junit.xml -v pytest_harvest/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-harvest.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-harvest.git <feature_branch> --no-commit
Finally review the changes, possibly perform some modifications, and commit.