In order to help contributors figure out how to effectively test their changes we should add some additional recommendations for running the unit tests to our contributor testing docs
To the question "why not use tox": the tox setup seems a little broken to me as there's no way to run a single test because the default environment runs coverage... I've tried to write a new environment config for that but it becomes a little clunky. Calling "python3 -m unittest" seems fine to me: I just didn't know it
FYI, you can run unittest-powerd modules/classes/tests directly like so:
python test_repository_tool.py # Runs all test cases (classes) in that test suite (module)
python test_repository_tool.py TestRepository # Runs all tests (functions) in TestRepository test case
python test_repository_tool.py TestRepository.test_writeall # Runs test_writeall test only
Originally posted by @lukpueh in #1067 (comment)
In order to help contributors figure out how to effectively test their changes we should add some additional recommendations for running the unit tests to our contributor testing docs
FYI, you can run
unittest-powerd modules/classes/tests directly like so:Originally posted by @lukpueh in #1067 (comment)