Hi Benji, Adam
Betreff: Re: [Zope-dev] zope.testing 3.6.0 released
Hello Benji,
I think we solved that problem at the Blackforest sprint in
Freiburg with Roger. As I remember there are tests for that too.
Yes, we solved the issue that the coverage feature
was loaded after the import
Hello,
Seems like 86460 breaks it.
I have some idea why testrunner-coverage.txt does not detect this.
I think it is doing coverage just on the tests code. There seems to be
no application-like code. All code seems to come from testcases,
doctests, docfiles. So far I can see.
Right now I'm under
Hey Benji,
Seems that it breaks coverage...
The result looks like coverage is started after importing the modules
to test. That means declarations do not seem to 'run', but just the code
inbetween them.
Checked with 3.5.1, it looks fine.
--
Best regards,
Adam GROSZER
On Wed, Jul 16, 2008 at 1:19 PM, Adam GROSZER [EMAIL PROTECTED] wrote:
Hey Benji,
Seems that it breaks coverage...
In what way is coverage broken? With or without -j? Can you formulate
a test that demonstrates the breakage?
The result looks like coverage is started after importing the
Hello Benji,
Sorry, now being specific with the facts (all other activities only
tomorrow (I'll check the revisions))
Results are generated by:
python bootstrap.py
bin/buildout
bin/coverage-test
bin/coverage-report
on the source of:
3.6.0 of zope.testing is out with my subprocess parallelization branch
merged (plus I fixed a few bugs in the trunk). There were several
other changes, here's the pertinent part of the release notes:
- Added -j option to parallel tests run in subprocesses.
- RENormalizer accepts plain Python
