testing "all" module tests almost nothing

[Alexandre Fayolle - camptocamp]

Hi,

reading the code of the recipe, I found in postbuildout.py install_modules_test_openerp:

    steps.append(ShellCommand(command=[
        'bin/test_openerp', '-i',
        comma_list_sanitize(options.get('openerp-addons', 'all')),

and I thought "nice, I can use 'all' or even omit openerp-addons and this will run the tests for all modules"

It turns out that it does not : bin/start_openerp --stop-after-init -i all does not install anything apart from base and the web addons.

[Georges Racinet (gracinet)]

Yes, that's been a problem from the very beginning, and we let it go for long because we could live with an explicit list (especially in the case of customer projects). And at that time, nobody seemed to care about launching the tests for all modules within a buildbot.

Recently, however, this configurator got a new 'subfactory' to use 'openerp-command initialize; to the same effect, with the added benefit that we get a clean error if that fails. I'm not sure that's documented yet.

You can find an example shipping with anybox.buildbot.openerp : ocb-7.0. Getting back to revision 289 to get it without the improved reports:

[buildout]
parts = openerp
find-links = http://download.gna.org/pychart/
versions = versions

extensions = gp.vcsdevelop
vcs-extend-develop =
    bzr+http://bazaar.launchpad.net/~openerp/openerp-command/7.0#egg=openerpcommand
vcs-update = True

Then, in the MANIFEST.cfg, you may put this:

post-buildout-steps = openerpcommand-initialize-tests

[Georges Racinet (gracinet)]

Forgot to state the obvious : having a perfectly working solution makes the motivation to fix the 'standard' post-buildout a bit low.