unittest problems

Richard Wesley hawkfish at trustedmedianetworks.com
Wed Jul 30 19:55:37 CEST 2003

In article <87el095733.fsf at pobox.com>, jjl at pobox.com (John J. Lee) 

> Richard Wesley <hawkfish at trustedmedianetworks.com> writes:
> > I am trying to retrofit some units test into our code using the unittest 
> > module.  I can get individual rewrites to work, but I am having trouble 
> > writing the "one test to run them all and in the darkness bind them" 
> > script.  There are two main sources of trouble:
> > 
> > - Test data that is stored next to the script that uses it;
> > - Several levels of scripts (top/utils/tests) with tests/data scattered 
> > at all levels;
> > 
> > Are there any good examples out there of a more complex set of tests in 
> > a multilevel tree/package with attached test data?  What about standard 
> > conventions for hooking stuff together (suite(), etc.)?
> <http://www.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=873ci3lk2o.fsf%40pobo
> x.com&rnum=1&prev=/groups%3Fas_q%3Dunittest%26safe%3Dimages%26ie%3DISO-8859-1%
> 26as_uauthors%3Djjl%40pobox.com%26lr%3D%26num%3D30%26hl%3Den>
> http://tinyurl.com/ig2q


My problem turned out to be that the existing code had lots of relative 
import statements (from FileInSameDir import blah) which caused import 
to barf when called from a different level in the tree.  Not to mention 
a few missing __init__.py files.  Once I cleaned everything up, it all 
worked and the main unit_test.py will run everything.   I used your 
code, driving it with the results of os.path.walk and parameterizing the 
pattern as a list (we have two test case file name patterns, one for 
intercaps and one for _).


- rmgw


Richard Wesley                                  Trusted Media Networks, Inc.

"'And now', cried Max, 'let the wild rumpus start!'" 
    - Maurice Sendak, _Where The Wild Things Are_

More information about the Python-list mailing list