Baiju M wrote:
Hi,
I am thinking about organizing a Zope 3 Egg Day for eggification
of zope.app.* packages. Anyone interested?
Eggification of zope.app.* packages is a massive effort, so it's not yet
added to the release goal of Zope 3.4. If this egg day become successful,
I think we
On Fri, Jan 12, 2007 at 08:07:22AM +0530, Baiju M wrote:
Marius Gedminas wrote:
Log message for revision 71953: Implement a --list-modules option
that lists all modules matching your pattern, but does not actually
run any tests.
I hope this will help me figure out why test.py -s
Marius Gedminas wrote:
[snip]
And all tests are passed with message Ran 123 tests with 0
failures and 0 errors in 18.783 seconds.
Which Python version do you have? I get 4 failures with Python
2.4.4c1 (Ubuntu Edgy) with the zope.testing trunk. These are now
fixed on the mgedmin-fixes
The Zope 3 test runner can filter tests by package, module, test name and
layer. Sometimes your expectations do not match reality and either the
test you want is not being run, or more tests than you wanted are being run.
When you want to debug filter patterns it helps if you can see what
tests
Marius Gedminas wrote:
I have implemented a --list-modules option in a branch. It causes the
test runner to apply package and module name filters, and then print the
list of Python module names that would be imported. It is very fast
because it doesn't actually import the modules. It is not
On Fri, Jan 12, 2007 at 05:17:18PM -0500, Benji York wrote:
Marius Gedminas wrote:
I have implemented a --list-modules option in a branch. It causes the
test runner to apply package and module name filters, and then print the
list of Python module names that would be imported. It is very
Due to an accident of implementation, if you pass both -u (run unit
tests) and -f (run non-unit tests) to the test runner, it will not run
any tests at all. That is not useful.
I have a branch where test.py -fu is equivalent to specifying neither -f
nor -u and runs all the tests:
A long time ago test.py -s accepted directory names. Later it was
changed to take package names instead. There is some
backwards-compatibility code that replaces slashes with dots, but it is
incomplete: test.py -s src/zope would try to run the tests for a
nonexistent package src.zope.
I have
On Jan 12, 2007, at 6:33 PM, Marius Gedminas wrote:
On Fri, Jan 12, 2007 at 05:17:18PM -0500, Benji York wrote:
Marius Gedminas wrote:
I have implemented a --list-modules option in a branch. It
causes the
test runner to apply package and module name filters, and then
print the
list of
