roadrunner 0.1

Limitiations

Because it preloads the Plone environment you won’t be able to see changes to the Core Plone components. However, it should see all changes in your application code which is what you will most likely be changing anyways. Unless you are a core developer.

Theoretically this should be able to work with any test environment (eg. Django, TG, Twisted).

I eventually plan to do this, and would accept any patches in the meantime if anyone feels so inclined.

How to use it?

Roadrunner only currently works as part of a buildout.

Easiest way to try it is to add it to an existing Plone 3 buildout.

Here’s a sample part:

[roadrunner]
recipe = zc.recipe.egg
eggs =
    ${instance:eggs}
    roadrunner
extra-paths = ${instance:zope2-location}/lib/python
initialization =
    conf_file = "${instance:location}/etc/zope.conf"
arguments = conf_file, "${instance:zope2-location}", "${buildout:directory}"

Yes it’s ugly. It will get fixed eventually.

Then you can run roadrunner:

$ bin/roadrunner -s Products.PasswordResetTool

Author

Jordan Baker <jbb@scryent.com>

TODO

• ability to preload any arbitrary layers, plus some presets like –plone or –grok

• hooks for fixture configuration?

• tests… how ironic this code has none, but it started as a proof of concept