JeanMichel FRANCOIS <[email protected]> writes: > Self response, > > By pinning version of zope.testing to 3.7.1 in the buildout of > collective.loadtesting it works: > > [versions] > zope.testing=3.7.1
You got it! The 3.6.0 release of zope.testing refactored the large testrunner.py file into a testrunner/__init__.py package. I've put a 'zope.testing>=3.6' requirement into setup.py. Ross > Le Monday 16 March 2009 12:08:25 JeanMichel FRANCOIS, vous avez écrit : > >> Hi, >> i m currently give a try to collective.loadtesting. i want to integrate it >> in projects i m working on. >> the buildout is running well, but the tests fails: >> >> source bin/activate >> svn co https://svn.plone.org/svn/collective/collective.loadtesting/trunk> >> collective.loadtesting >> cd collective.loadtesting >> python bootstrap.py >> ./bin/buildout >> ./bin/fl-run-bench -s collective.coreloadtests -t test_ReadOnly --cycles=1 >> >> collective.coreloadtests -t test_ReadOnly --cycles=1 >> Traceback (most recent call last): >> File >> "/home/toutpt/workspace/performanceplone/collective.loadtesting/bin/fl- >> run-bench", line 19, in ? >> import collective.funkload.bench >> File >> "/home/toutpt/workspace/performanceplone/collective.loadtesting/src/collect >>ive.funkload/src/collective/funkload/bench.py", line 8, in ? >> from zope.testing.testrunner import runner >> ImportError: cannot import name runner >> >> So what i need to do ? I have take a look at zope.testing.testrunner and >> there are no 'runner' nor 'options' to be import by collective.funkload. > > _______________________________________________ > Product-Developers mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/product-developers _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
