--- /dev/null
+When running `python test.py` I recieved lots of errors due to 'tla'
+(the GNU Arch revision control system binary) not being installed.
+I had expected test.py to only test the backends for installed VCSs.
+
+I've added a note saying that `python test.py` tests *all* the
+backends, but someone who understands the usage better can probably
+write a nicer version.
--- /dev/null
+
+
+
+Content-type=text/plain
+
+
+
+
+
+
+Date=Thu, 13 Nov 2008 16:35:24 +0000
+
+
+
+
+
+
+From=wking
+
+
+
--- /dev/null
+Ideally the tests would fail gracefully with some simple message like
+"tla version control system not found", and we could skip the message
+in the test.py docstring.
--- /dev/null
+
+
+
+Content-type=text/plain
+
+
+
+
+
+
+Date=Thu, 13 Nov 2008 16:38:36 +0000
+
+
+
+
+
+
+From=wking
+
+
+
--- /dev/null
+
+
+
+creator=wking
+
+
+
+
+
+
+severity=minor
+
+
+
+
+
+
+status=open
+
+
+
+
+
+
+summary=Usage of be/test.py is unclear
+
+
+
+
+
+
+time=Thu, 13 Nov 2008 16:31:41 +0000
+
+
+
+"""Usage: python test.py [module]
+
+When called without an optional module name, run the doctests from
+*all* modules. This may raise lots of errors if you haven't installed
+one of the versioning control systems.
+
+When called with an optional module name, only run the doctests from
+that module.
+"""
+
from libbe import plugin
import doctest
import sys