|
|
Boost Testing : |
From: Jonathan Brandmeyer (jbrandmeyer_at_[hidden])
Date: 2005-05-15 21:16:37
On Sun, 2005-05-15 at 01:26 -0700, Victor A. Wagner Jr. wrote:
> I don't know why 7.1 says it's running (we don't get to see results of
> running things)
Change line 130 of args.py to:
return doctest.testmod(sys.modules.get(__name__), verbose=True)
to get verbose information when running the test manually and when you
want reports of successes as well as failures.
> but I know that if I funn args.py from my command line I
> get the same errors shown in results.
> I further note, that if I remove the '""" ........ """ from the .py file
> it claims it runs.
See the documentation for the Python doctest module. It will explain
the function of the multiline string.
> I was under the impression that everything between """ and another """ was
> comment
Actually, its a multiline string literal that contains a set of unit
tests.
> apparently something has changed in python 2.4, but I'm still baffled that
> the 7.1 says it's running.
To run the test manually, you have to do a little PYTHONPATH and PATH
manipulation to ensure that the right shared libraries are available to
Python. Run the test under bjam verbosely to figure out how it is
setting up the environment when running the test successfully under VC
7.1.
> It appears there's something amiss in the testing framework
Based on the first error message in each test for VC 8.0, I'll bet the
problem has to do with the PYTHONPATH and/or PATH used by bjam when it
is running the tests. For most of them, part of each test is a compiled
plugin to Python that must be loadable to run it. The key is the
ImportError.
One tip that might help you debug this is to add the line
>>> import sys; print sys.path
at the top of the file, within the triple-quoted string. This will
print out the Python module search path that is actually being used when
conducting the test.
HTH,
-Jonathan