Many thanks for Héctor Verlarde for encouraging us to try out Travis CI for testing our own Plone add-ons. Also, thanks for Godefroid Chapelle for showing me, how to run Selenium tests on a headless server, e.g. on Travis CI.
As you may already know, the main issue in testing Plone add-ons on Travis CI is its strict 15 minute time limit on running your test suite. And as you may also know, 15 minutes is not much time for our dear buildout to gather all the required dependencies of Plone or plone.app.testing, and still run our test after the buildout.
As expected, neither did I get far without having issues with the time limit. And for some reason, I couldn’t get the earlier solutions to work for me. Eventually, I found out a new solution, surprisingly, with the help of Plone Unified Installer.
Because Plone Unified Installer comes in a single downloadable package and includes a complete buildout-cache usable also in a test buildout, I realized, that it could speed up my test buildout a lot, and it did. Yet, with Plone 4.3 shipping with Dexterity, I would expect it to speed it up even more.
Enough talk. Here’s my setup:
buildout.cfg
[buildout]
extends = http://dist.plone.org/release/4.2.1/versions.cfg
develop = .
parts = test
versions = versions
[versions]
zc.buildout = 1.6.3
[test]
recipe = zc.recipe.testrunner
eggs = my_package [test]
Nothing special here. I’m not sure if zc.buildout = 1.6.3 makes any difference, but I added it nevertheless. Also, I expect setup.py of the tested package to include complete extras_require={'test': ... } with all the required dependencies for testing.
So, on a local machine, python bootstrap.py, bin/buildout and bin/testcombo should run tests for a freshly cloned package repository just as expected.
travis.cfg
[buildout]
extends = buildout.cfg
parts =
download
install
test
eggs-directory = buildout-cache/eggs
download-cache = buildout-cache/downloads
[download]
recipe = hexagonit.recipe.download
url = https://launchpad.net/plone/4.2/4.2.1/+download/Plone-4.2.1-UnifiedInstaller.tgz
[install]
recipe = collective.recipe.cmd
on_install = true
cmds = tar jxvf ${download:location}/Plone-4.2.1-UnifiedInstaller/packages/buildout-cache.tar.bz2 1>/dev/null
Here’s the magic for re-using Plone Unified Installer for your test buildout:
- Ar first, download and unpack the installer in
[download] part - then extract its buildout-cache in
[install] part into the locations defined in [buildout] part.
As you might guessed, after this, buildout needs to download only the extra requirements of the tested package! Long live Plone Unified Installer!
.travis.yml
language: python
python: "2.7"
install:
- mkdir -p buildout-cache/eggs
- mkdir -p buildout-cache/downloads
- python bootstrap.py -c travis.cfg
- bin/buildout -N -t 3 -c travis.cfg
script: bin/test
Note, how we create the buildout-cache-directories defined earlier in travis.cfg. The rest should be easy: we just do the bootstrap and run our tests with sane buildout-options, and… that’s all.
.travis.yml for robotsuite
Oh, in the beginning, I mentiond about learning something important from Godefroid. Well, if you have followed me on creating zope.testrunner-compatible Robot Framework -tests with plone.app.testing, you only need to add a few extra lines to make your Robot Framework tests runnable on Travis CI:
language: python
python: "2.7"
install:
- mkdir -p buildout-cache/eggs
- mkdir -p buildout-cache/downloads
- python bootstrap.py -c travis.cfg
- bin/buildout -N -t 3 -c travis.cfg
before_script:
- "export DISPLAY=:99.0"
- "sh -e /etc/init.d/xvfb start"
script: bin/test
If you think, this is cool, please, give some love for the Travis CI team.
