From bc0fa8d3795ed7e40aaa00f579bb2977897bce25 Mon Sep 17 00:00:00 2001 From: Michał Górny Date: Tue, 17 Jul 2018 21:50:45 +0200 Subject: Rename pym→lib, for better distutils-r1 interoperability MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Closes: https://github.com/gentoo/portage/pull/343 --- TEST-NOTES | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'TEST-NOTES') diff --git a/TEST-NOTES b/TEST-NOTES index f9c6ab0cd..8be5f9cf3 100644 --- a/TEST-NOTES +++ b/TEST-NOTES @@ -4,7 +4,7 @@ UnitTests Portage has some tests that use the unittest framework that ships with python (2.3-2.4ish) Tests have a specific naming convention. -in pym/portage/tests/ there is a runTest script that invokes pym/portage/tests/__init__.py +in lib/portage/tests/ there is a runTest script that invokes lib/portage/tests/__init__.py This init looks at a hardcoded list of test dirs to search for tests. If you add a new dir and don't see your new tests, make sure that the dir is in this list. @@ -15,14 +15,14 @@ you should have files of the form test_${function}.py. So if I was to write a vercmp test, and vercmp is in portage_versions. -pym/portage/tests/portage_versions/test_vercmp.py +lib/portage/tests/portage_versions/test_vercmp.py would be the filename. The __init__.py file now does recursive tests, but you need to tell it so. For example, if you had cache tests the dir format would be something like... -pym/portage/tests/cache/flat_hash/test_foo.py +lib/portage/tests/cache/flat_hash/test_foo.py and you would put "cache/flat_hash" into the testDirs variable in __init__.py. -- cgit v1.2.3-65-gdbad