Provide a "post buildout steps" for nose testing

[Georges Racinet]

See https://pypi.python.org/pypi/anybox.buildbot.openerp#custom-builds for "post buildout steps"

The sequence to perform for nosetests is indeed different: install modules, then launch nose.

It would be the same for openerp_command run-tests, btw

Will be done with options for coverage, profiling and uploading of resulting data to the buildbmaster.

[Georges Racinet (gracinet)]

Done, lacks documentation

The "post buildout steps" is called "nose". It has lots of options
Docstring says:

          - openerp-addons: comma-separated list of addons to test
          - nose.tests: goes directly to command line; list directories to find
            tests here.
          - nose.coverage: boolean, if true, will run coverage for the listed
            addons
          - nose.cover-options: additional options for nosetests invocation
          - nose.upload-path: path on master to upload files produced by nose
          - nose.upload-url: URL to present files produced by nose in waterfall

[Georges Racinet (gracinet)]

And I should mention "nose.profile" option (can be very stressful for low-end hardware, requires lots of RAM and upload bw)

[Georges Racinet (gracinet)]

Pushed yesterday, remember that the nose-tested addons must have the hack to avoid being imported twice (first nose, then OpenERP registry)

[Georges Racinet (gracinet)]

Released with 0.9