Changes between Version 10 and Version 11 of TracDev/UnitTests

Timestamp:

May 11, 2009, 10:38:16 AM (15 years ago)

Author:

Christian Boos

Comment:

added a #Troubleshooting section

TracDev/UnitTests

@@ -36 +36 @@
 }}}
 
-=== ImportError: no module named tests ===
-If you try to run the tests and you receive
-{{{
-ImportError: No module named tests 
-}}}
-
-It may mean that you have a version of Trac installed in /usr/lib/pythonX.X/site-packages but you are testing a different version installed elsewhere on your machine.
-
-If so, uninstalling the system version of Trac in /usr/lib/pythonX.X should allow you to run the unit tests, testing your private version.
-
-Installing your virtual environment with {{{--no-site-packages}}} should eliminate this problem.
 == Buildbots ==
 
@@ -78 +67 @@
 If these dependencies are not present, certain tests will be skipped.
 
+== Troubleshooting ==
+For general advice about Trac debugging, see TracTroubleshooting.
+
+=== !ImportError: no module named tests ===
+If you try to run the tests and you receive
+{{{
+ImportError: No module named tests 
+}}}
+
+It may mean that you have a version of Trac installed in /usr/lib/pythonX.X/site-packages but you are testing a different version installed elsewhere on your machine.
+
+If so, uninstalling the system version of Trac in /usr/lib/pythonX.X should allow you to run the unit tests, testing your private version.
+
+Installing your virtual environment with {{{--no-site-packages}}} should eliminate this problem.
+
 ----
 See also: TracDev/FunctionalTests