[ZCM] [ZC] 1478/ 5 Comment "test.py improvements"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #1478 Update (Comment) "test.py improvements"
 Status Pending, Zope/bug medium
To followup, visit:
  http://collector.zope.org/Zope/1478

==============================================================
= Comment - Entry #5 by shh on Aug 25, 2004 5:01 pm

Chris, this was part of the --config-file feature, so it's on Zope-2_7-branch and trunk.

For docs I suggest 'test.py --help' :-)
________________________________________
= Comment - Entry #4 by regebro on Aug 24, 2004 5:38 am

Have the docs been updated too? svn.zope.org is still down, so it's hard to tell...
________________________________________
= Comment - Entry #3 by chrisw on Aug 24, 2004 4:29 am

Stephan, what branches of SVN/CVS was this solved in, and what versions of Zope is it due to land in?

Once answered, we can mark this bug as resolved :-)
________________________________________
= Comment - Entry #2 by shh on Aug 23, 2004 4:04 pm

FWIW, your #1 is no longer an issue with test.py from CVS/SVN.
________________________________________
= Request - Entry #1 by regebro on Aug 23, 2004 11:18 am

1. Trailing slashes on --libdir path prevents test.py from finding the tests. So "bin/zopectrl run test.py --libdir Products" will work, but "bin/zopectrl run test.py --libdir Products/" finds no tests. This is extra annoying since the tab/completion in most shells adds a trailing slash...

2. Finding out exactly HOW to run unittest in 2.7 was not exactly easy. The docs are completely outdated and makes no mention of how to run tests at all, it just has outdated references on how to write them (with references to the non-existing lib/python/unittest.py, for example). Even zopewiki.org calls running unit tests a "terrifying black art"...
==============================================================