hamradio/chirp
1
0
Fork 0
mirror of https://github.com/kk7ds/chirp.git synced 2024-09-21 10:37:15 +00:00
Code Issues Packages Projects Releases Wiki Activity
3792acf9dc
chirp/tox.ini

64 lines
1.1 KiB
INI
Raw Normal View History

Add tox.ini for running tests Tox handles venv creation and management of setup install for running tests. Since we have a venv required already, this just makes sense. Now, instead of: ./run_all_tests.sh You can just run: tox Assuming you have tox installed (pip install tox). You can run individual test groups like this: tox -e unit tox -e driver and still pass arguments to the driver tests per usual with: tox -e driver -- -d Icom_IC-2200H I'll be working to make the build system use tox for running tests with better isolation and hopefully more repeatability. #5237
2017-10-12 03:37:37 +00:00
[tox]
[py3] Put a py3clean environment in the list before the py3 jobs This helps prevent python3 from stumbling over py2 cache files #495
2019-02-12 00:21:28 +00:00
envlist = unit,driver,style,py3clean,py3unit,py3driver
Make tox not generate sdist For speed. #0
2019-02-11 22:04:07 +00:00
skipsdist = True
Add tox.ini for running tests Tox handles venv creation and management of setup install for running tests. Since we have a venv required already, this just makes sense. Now, instead of: ./run_all_tests.sh You can just run: tox Assuming you have tox installed (pip install tox). You can run individual test groups like this: tox -e unit tox -e driver and still pass arguments to the driver tests per usual with: tox -e driver -- -d Icom_IC-2200H I'll be working to make the build system use tox for running tests with better isolation and hopefully more repeatability. #5237
2017-10-12 03:37:37 +00:00
[testenv]
basepython = python2.7
sitepackages = True
Make test adapter granular This makes the unit test adapter granular so you can run individual tests and drivers for quicker automated testing.
2021-12-06 17:31:15 +00:00
passenv = HOME CHIRP_TESTS CHIRP_TESTIMG
Add tox.ini for running tests Tox handles venv creation and management of setup install for running tests. Since we have a venv required already, this just makes sense. Now, instead of: ./run_all_tests.sh You can just run: tox Assuming you have tox installed (pip install tox). You can run individual test groups like this: tox -e unit tox -e driver and still pass arguments to the driver tests per usual with: tox -e driver -- -d Icom_IC-2200H I'll be working to make the build system use tox for running tests with better isolation and hopefully more repeatability. #5237
2017-10-12 03:37:37 +00:00
whitelist_externals = bash
Add future to tox config Related to #743
2019-07-12 02:32:29 +00:00
deps = future
Add tox.ini for running tests Tox handles venv creation and management of setup install for running tests. Since we have a venv required already, this just makes sense. Now, instead of: ./run_all_tests.sh You can just run: tox Assuming you have tox installed (pip install tox). You can run individual test groups like this: tox -e unit tox -e driver and still pass arguments to the driver tests per usual with: tox -e driver -- -d Icom_IC-2200H I'll be working to make the build system use tox for running tests with better isolation and hopefully more repeatability. #5237
2017-10-12 03:37:37 +00:00
[testenv:unit]
deps =
[py3] Finally, unified test running across all environments and pythons pytest doesn't support the loadTests() discovery protocol, which means it would not ever find the driver test adapter in tests/__init__.py. So, this adds another adapter just for pytest (et al) which will trigger the test loader and make it find them. Now, with all environments and python versions, you get nicer pytest output, and can use expressions to run subsets of tests, like: tox -epy3driver 880.*clone #495
2019-02-14 00:53:28 +00:00
pytest
Fix tox unit test requirement for mox library #0
2018-03-16 00:12:30 +00:00
mox
Add mock to the unit test environment Fixes the tests for #5995
2018-08-08 14:30:15 +00:00
mock
[py3] Include future in the py2 test environment #495
2019-02-10 22:41:34 +00:00
future
Include pytest-xdist in the test environments Now that everything runs under pytest, I can run the entire suite on both pythons in just over two minutes with "tox -- -n auto --dist=loadscope" #0
2019-02-14 14:39:04 +00:00
pytest-xdist
Add tox.ini for running tests Tox handles venv creation and management of setup install for running tests. Since we have a venv required already, this just makes sense. Now, instead of: ./run_all_tests.sh You can just run: tox Assuming you have tox installed (pip install tox). You can run individual test groups like this: tox -e unit tox -e driver and still pass arguments to the driver tests per usual with: tox -e driver -- -d Icom_IC-2200H I'll be working to make the build system use tox for running tests with better isolation and hopefully more repeatability. #5237
2017-10-12 03:37:37 +00:00
commands =
[py3] Finally, unified test running across all environments and pythons pytest doesn't support the loadTests() discovery protocol, which means it would not ever find the driver test adapter in tests/__init__.py. So, this adds another adapter just for pytest (et al) which will trigger the test loader and make it find them. Now, with all environments and python versions, you get nicer pytest output, and can use expressions to run subsets of tests, like: tox -epy3driver 880.*clone #495
2019-02-14 00:53:28 +00:00
pytest --disable-warnings -v tests/unit {posargs}
Add tox.ini for running tests Tox handles venv creation and management of setup install for running tests. Since we have a venv required already, this just makes sense. Now, instead of: ./run_all_tests.sh You can just run: tox Assuming you have tox installed (pip install tox). You can run individual test groups like this: tox -e unit tox -e driver and still pass arguments to the driver tests per usual with: tox -e driver -- -d Icom_IC-2200H I'll be working to make the build system use tox for running tests with better isolation and hopefully more repeatability. #5237
2017-10-12 03:37:37 +00:00
python ./share/make_supported.py /dev/null
[testenv:driver]
[py3] Include future in the py2 test environment #495
2019-02-10 22:41:34 +00:00
deps =
future
[py3] Finally, unified test running across all environments and pythons pytest doesn't support the loadTests() discovery protocol, which means it would not ever find the driver test adapter in tests/__init__.py. So, this adds another adapter just for pytest (et al) which will trigger the test loader and make it find them. Now, with all environments and python versions, you get nicer pytest output, and can use expressions to run subsets of tests, like: tox -epy3driver 880.*clone #495
2019-02-14 00:53:28 +00:00
pytest
Include pytest-xdist in the test environments Now that everything runs under pytest, I can run the entire suite on both pythons in just over two minutes with "tox -- -n auto --dist=loadscope" #0
2019-02-14 14:39:04 +00:00
pytest-xdist
Add tox.ini for running tests Tox handles venv creation and management of setup install for running tests. Since we have a venv required already, this just makes sense. Now, instead of: ./run_all_tests.sh You can just run: tox Assuming you have tox installed (pip install tox). You can run individual test groups like this: tox -e unit tox -e driver and still pass arguments to the driver tests per usual with: tox -e driver -- -d Icom_IC-2200H I'll be working to make the build system use tox for running tests with better isolation and hopefully more repeatability. #5237
2017-10-12 03:37:37 +00:00
commands =
[py3] Finally, unified test running across all environments and pythons pytest doesn't support the loadTests() discovery protocol, which means it would not ever find the driver test adapter in tests/__init__.py. So, this adds another adapter just for pytest (et al) which will trigger the test loader and make it find them. Now, with all environments and python versions, you get nicer pytest output, and can use expressions to run subsets of tests, like: tox -epy3driver 880.*clone #495
2019-02-14 00:53:28 +00:00
pytest --disable-warnings -v tests/test_drivers.py {posargs}
Add tox.ini for running tests Tox handles venv creation and management of setup install for running tests. Since we have a venv required already, this just makes sense. Now, instead of: ./run_all_tests.sh You can just run: tox Assuming you have tox installed (pip install tox). You can run individual test groups like this: tox -e unit tox -e driver and still pass arguments to the driver tests per usual with: tox -e driver -- -d Icom_IC-2200H I'll be working to make the build system use tox for running tests with better isolation and hopefully more repeatability. #5237
2017-10-12 03:37:37 +00:00
[testenv:style]
Run tests in github workflow for py3
2022-09-09 15:09:37 +00:00
basepython = python3
sitepackages = False
Add tox.ini for running tests Tox handles venv creation and management of setup install for running tests. Since we have a venv required already, this just makes sense. Now, instead of: ./run_all_tests.sh You can just run: tox Assuming you have tox installed (pip install tox). You can run individual test groups like this: tox -e unit tox -e driver and still pass arguments to the driver tests per usual with: tox -e driver -- -d Icom_IC-2200H I'll be working to make the build system use tox for running tests with better isolation and hopefully more repeatability. #5237
2017-10-12 03:37:37 +00:00
deps =
Run tests in github workflow for py3
2022-09-09 15:09:37 +00:00
pep8
Add future to tox config Related to #743
2019-07-12 02:32:29 +00:00
future
Add tox.ini for running tests Tox handles venv creation and management of setup install for running tests. Since we have a venv required already, this just makes sense. Now, instead of: ./run_all_tests.sh You can just run: tox Assuming you have tox installed (pip install tox). You can run individual test groups like this: tox -e unit tox -e driver and still pass arguments to the driver tests per usual with: tox -e driver -- -d Icom_IC-2200H I'll be working to make the build system use tox for running tests with better isolation and hopefully more repeatability. #5237
2017-10-12 03:37:37 +00:00
commands =
Run tests in github workflow for py3
2022-09-09 15:09:37 +00:00
python3 ./tools/cpep8.py
[py3] Make setup.py compatible and start a new py3 tox environment Right now, this runs just the bitwise tests which are the only ones that work on py3. #495
2019-02-07 16:38:38 +00:00
[py3] Put a py3clean environment in the list before the py3 jobs This helps prevent python3 from stumbling over py2 cache files #495
2019-02-12 00:21:28 +00:00
[textenv:py3clean]
commands =
py3clean chirp tests
[py3] Split py3 tox environment into py3unit and py3driver #495
2019-02-09 20:36:04 +00:00
[testenv:py3unit]
[py3] Make setup.py compatible and start a new py3 tox environment Right now, this runs just the bitwise tests which are the only ones that work on py3. #495
2019-02-07 16:38:38 +00:00
basepython = python3
sitepackages = False
[py3]: Fix run_tests.py: - Import hack to work from a variety of places. This is really ugly, but these are going away once the driver files can at least be imported. - Something in the 2to3ing earlier broke the settings tests. Had to add len and getitem to RadioSettingValueString, which caused an infinite loop in the test's compare_settings. I dunno what I was thinking with the latter, but it seems like a infinite loop waiting to happen and it's hard to see through the blur how that ever worked. #495
2019-02-08 21:15:09 +00:00
setenv =
PYTHONPATH=../..
[py3] Make setup.py compatible and start a new py3 tox environment Right now, this runs just the bitwise tests which are the only ones that work on py3. #495
2019-02-07 16:38:38 +00:00
deps =
-rrequirements.txt
[py3] Changes to make test_chirp_common (and deps) work on py3 This is enough to be able to use pytest too, so convert to that. #495
2019-02-07 17:12:58 +00:00
-rtest-requirements.txt
[py3] Make setup.py compatible and start a new py3 tox environment Right now, this runs just the bitwise tests which are the only ones that work on py3. #495
2019-02-07 16:38:38 +00:00
commands =
[py3] Finally, unified test running across all environments and pythons pytest doesn't support the loadTests() discovery protocol, which means it would not ever find the driver test adapter in tests/__init__.py. So, this adds another adapter just for pytest (et al) which will trigger the test loader and make it find them. Now, with all environments and python versions, you get nicer pytest output, and can use expressions to run subsets of tests, like: tox -epy3driver 880.*clone #495
2019-02-14 00:53:28 +00:00
pytest --disable-warnings -v tests/unit {posargs}
[py3] Split py3 tox environment into py3unit and py3driver #495
2019-02-09 20:36:04 +00:00
[testenv:py3driver]
basepython = python3
sitepackages = False
setenv =
PYTHONPATH=../..
CHIRP_DEBUG=y
deps = {[testenv:py3unit]deps}
commands =
[py3] Finally, unified test running across all environments and pythons pytest doesn't support the loadTests() discovery protocol, which means it would not ever find the driver test adapter in tests/__init__.py. So, this adds another adapter just for pytest (et al) which will trigger the test loader and make it find them. Now, with all environments and python versions, you get nicer pytest output, and can use expressions to run subsets of tests, like: tox -epy3driver 880.*clone #495
2019-02-14 00:53:28 +00:00
pytest --disable-warnings -v tests/test_drivers.py {posargs}
Reference in New Issue Copy Permalink