Aaron Whitehouse has proposed merging lp:~aaron-whitehouse/duplicity/08-README-TESTING into lp:duplicity.
Commit message: Change README-TESTING to be correct for running individual tests now that we have moved to Pytest. Requested reviews: duplicity-team (duplicity-team) For more details, see: https://code.launchpad.net/~aaron-whitehouse/duplicity/08-README-TESTING/+merge/364214 -- Your team duplicity-team is requested to review the proposed merge of lp:~aaron-whitehouse/duplicity/08-README-TESTING into lp:duplicity.
=== modified file 'README-TESTING' --- README-TESTING 2017-05-14 07:17:59 +0000 +++ README-TESTING 2019-03-10 13:48:02 +0000 @@ -1,7 +1,7 @@ # Testing duplicty ## Introduction -Duplicitys test concept bases on unit test. +Duplicity's test concept bases on unit test. All tests are contained in the /testing folder of the main repository. As to see in the following sketch, there are several levels of testing duplicity and each can be used directly. @@ -46,14 +46,17 @@ from the main duplicity folder. You can run specific tests using: -‘tox -- -s [folder].[folder].[file].[class].[test]‘ +‘tox -- [test filename][::TestClassName::test_method]‘ For example: -‘tox -- -s testing.unit.test_selection‘ +‘tox -- testing/unit/test_selection.py‘ or: -‘tox -- -s testing.unit.test_selection.MatchingTest.test_tuple_include‘ +‘tox -- testing/unit/test_selection.py::MatchingTest::test_tuple_include‘ You can test against a single environment, e.g. ‘tox -e py27‘ + +Or stack these together, e.g. +‘tox -e py3 -- testing/unit/test_selection.py::MatchingTest::test_tuple_include‘ for example if you are working on fixing a bug, but please do a full run-tests before submitting a merge request.
_______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
