Instead of having running test installing eggs with setuptools during python setup.py test, which fails for caucase because one of its dependency (namely cryptography) cannot be installed so easily, we want to install the dependencies via buildout, using the same installation methods than in the actual software profiles using our eggs.

What I initially believed would be a small change turned out to be a long journey, especially because of using a develop version of slapos.recipe.cmmi caused signature changes in the parts installed by this recipe ( git, openssl etc - some parts that takes a bit of time to install ) so I had to fight with the software being reinstalled each time. Even though the cases which leads to reinstallation are understood (this even involved fixing a bug in buildout slapos.buildout!14 (merged) ), this is still the case. Some solutions are proposed in the commit message of f4b6eeda , but this reached a state where we can consider first merging with this known problem or discuss ways of improving that before merging if it's considered as blocking. Current state is that it takes one hour to re-install what has to be reinstalled and run the test suite on test runner.

Despite this issue, this approach already improve things, because:

• caucase tests are running (and passing)
• some slapos.cookbook are improved so that they reuse eggs from the buildout and do not install again eggs when the are run.
• ... and some other small cleanups

This depends on erp5!619 (merged) on the erp5.util side.