shadowfacts/fonttools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
fonttools/tox.ini

77 lines
1.7 KiB
INI
Raw Normal View History

tox.ini: configure tox test environment; set up py.test to discover both doctest and unittest tests
2015-12-12 17:52:18 +00:00
[tox]
tox.ini: require at least tox >= 3.0
2018-07-25 19:12:17 +01:00
minversion = 3.0
tox: add extras; allow to test with/without lxml calling 'tox -e py37-cov-nolxml' will run tests without lxml, using built-in ElementTree library
2018-10-18 15:35:02 +01:00
envlist = py{27,37}-cov, htmlcov
tox.ini: configure tox test environment; set up py.test to discover both doctest and unittest tests
2015-12-12 17:52:18 +00:00
[testenv]
deps =
tox.ini: require coverage>=4.3 Coverage 4.3 was released, it includes this patch: https://bitbucket.org/ned/coveragepy/pull-requests/118/check-source-isdir-not-just-exists-there/diff
2016-12-31 13:33:24 +01:00
cov: coverage>=4.3
tox.ini: configure tox test environment; set up py.test to discover both doctest and unittest tests
2015-12-12 17:52:18 +00:00
pytest
-rrequirements.txt
tox: add extras; allow to test with/without lxml calling 'tox -e py37-cov-nolxml' will run tests without lxml, using built-in ElementTree library
2018-10-18 15:35:02 +01:00
extras =
ufo
woff
unicode
interpolatable
!nolxml: lxml
tox.ini: configure tox test environment; set up py.test to discover both doctest and unittest tests
2015-12-12 17:52:18 +00:00
commands =
tox: add extras; allow to test with/without lxml calling 'tox -e py37-cov-nolxml' will run tests without lxml, using built-in ElementTree library
2018-10-18 15:35:02 +01:00
# test with or without coverage, passing extra positonal args to pytest
[tox] call pytest without --pyargs option Previously, we were using --pyargs to make sure pytest would run the test suite against the installed package, because our tests were embedded inside the package and hence importable. Now that they are placed in an external folder, that option is not needed. pytest without options will run all the test modules from the default test paths as defined in setup.cfg, i.e Tests/ folder. The tests will be run against the installed fontTools in the current tox environment. We also pass {posargs} in the 'htmlcov' tox env, to allow passing extra options after `tox -e htmlcov -- {posargs}` to the `coverage html` command.
2017-01-15 22:04:39 +00:00
cov: coverage run --parallel-mode -m pytest {posargs}
tox: remove unnecessary 'nocov' factor tox now allows to use exclamation mark to negate an environment factor.
2018-10-18 15:39:18 +01:00
!cov: pytest {posargs}
tox.ini: configure tox test environment; set up py.test to discover both doctest and unittest tests
2015-12-12 17:52:18 +00:00
tox.ini: use coverage.py instead of pytest-cov; run in --parallel-mode; use codecov instead of coveralls We no longer use coverage.py through the pytest-cov plugin, as it does not support --parallel-mode (or at least I wasn't able to figure it out). We run pytest through `coverage run -m pytest` instead, which does the same as `pytest --cov`. Running `tox` locally by default will now run pytest and coverage on 2.7, 3.5 and 3.6; it will then combine coverage data from all three, and finally generate a coverage report in htmlcov/index.html We need tp temporarily install coverage.py from the mercurial repo instead of the latest release because we require a patch that is not available yet with coverage 4.2: https://bitbucket.org/ned/coveragepy/pull-requests/118/check-source-isdir-not-just-exists-there/diff Finally, I replaced Coveralls with Codecov, as the latter is better designed and also supports Appveyor.
2016-12-26 13:49:31 +00:00
[testenv:htmlcov]
[tox] add 'coverage' toxenv to make local html coverage report This is useful if one wants to run coverage tests locally, and get a nice HTML report while one is writing tests. Just run: $ tox -e coverage -- {optional pytest arguments} And you get a "htmlcov/index.html" to view in your browser.
2016-10-14 15:18:28 +01:00
deps =
tox.ini: require coverage>=4.3 Coverage 4.3 was released, it includes this patch: https://bitbucket.org/ned/coveragepy/pull-requests/118/check-source-isdir-not-just-exists-there/diff
2016-12-31 13:33:24 +01:00
coverage>=4.3
[tox] add 'coverage' toxenv to make local html coverage report This is useful if one wants to run coverage tests locally, and get a nice HTML report while one is writing tests. Just run: $ tox -e coverage -- {optional pytest arguments} And you get a "htmlcov/index.html" to view in your browser.
2016-10-14 15:18:28 +01:00
skip_install = true
tox.ini: use coverage.py instead of pytest-cov; run in --parallel-mode; use codecov instead of coveralls We no longer use coverage.py through the pytest-cov plugin, as it does not support --parallel-mode (or at least I wasn't able to figure it out). We run pytest through `coverage run -m pytest` instead, which does the same as `pytest --cov`. Running `tox` locally by default will now run pytest and coverage on 2.7, 3.5 and 3.6; it will then combine coverage data from all three, and finally generate a coverage report in htmlcov/index.html We need tp temporarily install coverage.py from the mercurial repo instead of the latest release because we require a patch that is not available yet with coverage 4.2: https://bitbucket.org/ned/coveragepy/pull-requests/118/check-source-isdir-not-just-exists-there/diff Finally, I replaced Coveralls with Codecov, as the latter is better designed and also supports Appveyor.
2016-12-26 13:49:31 +00:00
commands =
coverage combine
[tox] don't pass {posargs} to coverage in 'htmlcov' env The {posargs} are global for the current tox process, and we already use them to pass additional arguments to the pytest command in the default testenv, so we can't at the same time also use them to pass options to coverage.py. The 'htmlcov' tox environment produces the combined coverage.py report, and store it in htmlcov/index.html; this is listed in the tox.ini 'envlist', so it is run by default at every 'tox' invocation, when no explicit env list is passed via either -e option or $TOXENV variable. The options to `coverage html` are not much interesting anyway; it's much more useful being able to, e.g., run tox for specific tests matching a string or expression: $ tox -- -k "feaLib"
2017-04-10 12:23:12 +01:00
coverage html
[tox] add 'coverage' toxenv to make local html coverage report This is useful if one wants to run coverage tests locally, and get a nice HTML report while one is writing tests. Just run: $ tox -e coverage -- {optional pytest arguments} And you get a "htmlcov/index.html" to view in your browser.
2016-10-14 15:18:28 +01:00
tox.ini: use coverage.py instead of pytest-cov; run in --parallel-mode; use codecov instead of coveralls We no longer use coverage.py through the pytest-cov plugin, as it does not support --parallel-mode (or at least I wasn't able to figure it out). We run pytest through `coverage run -m pytest` instead, which does the same as `pytest --cov`. Running `tox` locally by default will now run pytest and coverage on 2.7, 3.5 and 3.6; it will then combine coverage data from all three, and finally generate a coverage report in htmlcov/index.html We need tp temporarily install coverage.py from the mercurial repo instead of the latest release because we require a patch that is not available yet with coverage 4.2: https://bitbucket.org/ned/coveragepy/pull-requests/118/check-source-isdir-not-just-exists-there/diff Finally, I replaced Coveralls with Codecov, as the latter is better designed and also supports Appveyor.
2016-12-26 13:49:31 +00:00
[testenv:codecov]
passenv = *
tox.ini: configure coveralls
2016-04-11 00:17:14 +01:00
deps =
tox.ini: require coverage>=4.3 Coverage 4.3 was released, it includes this patch: https://bitbucket.org/ned/coveragepy/pull-requests/118/check-source-isdir-not-just-exists-there/diff
2016-12-31 13:33:24 +01:00
coverage>=4.3
tox.ini: use coverage.py instead of pytest-cov; run in --parallel-mode; use codecov instead of coveralls We no longer use coverage.py through the pytest-cov plugin, as it does not support --parallel-mode (or at least I wasn't able to figure it out). We run pytest through `coverage run -m pytest` instead, which does the same as `pytest --cov`. Running `tox` locally by default will now run pytest and coverage on 2.7, 3.5 and 3.6; it will then combine coverage data from all three, and finally generate a coverage report in htmlcov/index.html We need tp temporarily install coverage.py from the mercurial repo instead of the latest release because we require a patch that is not available yet with coverage 4.2: https://bitbucket.org/ned/coveragepy/pull-requests/118/check-source-isdir-not-just-exists-there/diff Finally, I replaced Coveralls with Codecov, as the latter is better designed and also supports Appveyor.
2016-12-26 13:49:31 +00:00
codecov
tox.ini: configure coveralls
2016-04-11 00:17:14 +01:00
skip_install = true
ignore_outcome = true
tox.ini: use coverage.py instead of pytest-cov; run in --parallel-mode; use codecov instead of coveralls We no longer use coverage.py through the pytest-cov plugin, as it does not support --parallel-mode (or at least I wasn't able to figure it out). We run pytest through `coverage run -m pytest` instead, which does the same as `pytest --cov`. Running `tox` locally by default will now run pytest and coverage on 2.7, 3.5 and 3.6; it will then combine coverage data from all three, and finally generate a coverage report in htmlcov/index.html We need tp temporarily install coverage.py from the mercurial repo instead of the latest release because we require a patch that is not available yet with coverage 4.2: https://bitbucket.org/ned/coveragepy/pull-requests/118/check-source-isdir-not-just-exists-there/diff Finally, I replaced Coveralls with Codecov, as the latter is better designed and also supports Appveyor.
2016-12-26 13:49:31 +00:00
commands =
coverage combine
codecov --env TOXENV
build sdist/wheel only once for both Github and PyPI This makes sure we upload the same files to Github Releases and PyPI. Currently we were building them twice, with the risk of different files being uploaded to the two repositories.
2016-12-26 19:36:08 +00:00
tox: add env to check package long_description using 'twine check' command Restrucutred Text is very picky. 3.32.0 release process failed because of some broken rst. I have to stop doing [skip ci] when I update the changelog... :(
2018-11-01 13:11:12 +00:00
[testenv:package_readme]
description = check that the long description is valid (need for PyPi)
deps = twine >= 1.12.1
pip >= 18.0.0
skip_install = true
extras =
commands = pip wheel -w {envtmpdir}/build --no-deps .
twine check {envtmpdir}/build/*
build sdist/wheel only once for both Github and PyPI This makes sure we upload the same files to Github Releases and PyPI. Currently we were building them twice, with the risk of different files being uploaded to the two repositories.
2016-12-26 19:36:08 +00:00
[testenv:bdist]
deps =
setuptools
wheel
skip_install = true
install_command =
# make sure we use the latest setuptools and wheel
pip install --upgrade {opts} {packages}
whitelist_externals =
rm
commands =
# clean up build/ and dist/ folders
[travis] use twine to upload to PyPI
2018-09-11 12:09:50 +02:00
python -c 'import shutil; shutil.rmtree("dist", ignore_errors=True)'
build sdist/wheel only once for both Github and PyPI This makes sure we upload the same files to Github Releases and PyPI. Currently we were building them twice, with the risk of different files being uploaded to the two repositories.
2016-12-26 19:36:08 +00:00
python setup.py clean --all
# build sdist
python setup.py sdist --dist-dir {toxinidir}/dist
# build wheel from sdist
pip wheel -v --no-deps --no-index --wheel-dir {toxinidir}/dist --find-links {toxinidir}/dist fonttools
[travis] use twine to upload to PyPI
2018-09-11 12:09:50 +02:00
[testenv:pypi]
deps =
{[testenv:bdist]deps}
twine
skip_install = true
passenv = TWINE_USERNAME TWINE_PASSWORD
commands =
{[testenv:bdist]commands}
twine upload dist/*.whl dist/*.zip
Reference in New Issue Copy Permalink