summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlec Warner <antarus@gentoo.org>2007-02-10 03:19:01 +0000
committerAlec Warner <antarus@gentoo.org>2007-02-10 03:19:01 +0000
commitc4be6a090b3766bc00540e762a482723c11297b2 (patch)
treed10dfd527714a97c531e61f805f60b8c49a1b0ce
parentc17adabeb018c9f425a1e97ac79f16514afa2381 (diff)
downloadportage-c4be6a090b3766bc00540e762a482723c11297b2.tar.gz
portage-c4be6a090b3766bc00540e762a482723c11297b2.tar.bz2
portage-c4be6a090b3766bc00540e762a482723c11297b2.zip
update test notes
svn path=/main/trunk/; revision=5934
-rw-r--r--TEST-NOTES11
1 files 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)