From c4be6a090b3766bc00540e762a482723c11297b2 Mon Sep 17 00:00:00 2001 From: Alec Warner Date: Sat, 10 Feb 2007 03:19:01 +0000 Subject: [PATCH] update test notes svn path=/main/trunk/; revision=5934 --- TEST-NOTES | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/TEST-NOTES b/TEST-NOTES index 82f342310..32db45a6d 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 tests/ there is a runTest script that invokes tests/__init__.py +in pym/portage/tests/ there is a runTest script that invokes pym/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,13 +15,18 @@ 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. -tests/portage_versions/test_vercmp.py +pym/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... -tests/cache/flat_hash/test_foo.py +pym/portage/tests/cache/flat_hash/test_foo.py and you would put "cache/flat_hash" into the testDirs variable in __init__.py. + +emerge +------ + +The emerge namespace currently has 0 tests (and no runner) -- 2.26.2