But how much does it makes sense to write acceptance tests while creating screenshots for new blog posts presenting Plone add-ons?
I have a new experimental project:
What you should see, is A Sphinx-built blog written in ReStructuredText being built, including annotated screenshots generated from embedded Robot Framework -acceptance tests describing a Plone add-on. (Technically, each blog post could present different add-ons.)
The resulting blog could be hosted on GitHub, served via GitHub-pages and it should be possible to edit it collaborately using branching/forking and pull-requests.
I'm not sure if this would really work out, and won't include this in Planet yet, but you can see the preview at
and example configuration with raw posts at
and ping me at Twitter or IRC, if you are interested in participating.
- sphinxcontrib-robotframework is a Robot Framework integration for Sphinx, which is created by me and Vivek Kumar Verma as a GSOC2013-project, which I mentored.
- robotframework-selenium2screenshots is a PIL and jQuery-based screenshot annotation and cropping library for Robot Framework, which I started during PLOG2013 for plone.app.robotframework, but released as a separate package to make it available outside Plone-projects also. Of course, it requires also robotframework-selenium2library.
- plone.app.robotframework comes with Godefroid Chapelle's Zope2Server-library, which allows to start Plone test fixtures directly from Robot Framework test suites (without zope.testrunner or robotsuite).
- Tinkerer is a blogging engined built on top of Sphinx written by Vlad Riscutia.