The release comes with several syntax improvements:

• Multiple selectors are allowed in the same rule.
  

• Value providers can be recursive.

• url() and alias() value providers.

• Node selection can be specified together with client actions.

• Full form submits can be specified together with actions.

More details can be read in the release notes.

The following packages have been released, to be used with both Zope 2.10 or higher, and Zope3.

There is a howto available that answers common setup and usage questions.

Plone 3.1 includes KSS 1.4. The Plone specific version of the same howto is here.

Many thanks to anyone who worked on the KSS code, and made this new release possible.

We had a great time in Sorrento this year. The KSS work was centered around testing Plone and the PSPS #7841 topic.

• Simone Deponti, Tom "Spanky" Kapanka, and Balázs Reé worked on extending the kss.demo testrunner to deal better with application level selenium tests. Besides testing Plone itself, it also aims at enabling testing of applications written with Plone, Zope or Grok.
  
• Beppe Zizza wrote documentation that explains how to install the test running environment, how to run the existing tests, and how to write new ones, The document is targeted towards Plone developers but is also meant to be generic with respect to other Zope based frameworks.
• Simone Deponti and Massimo Azzolini championed the review of the Plone tests we wrote last year. They fixed those and tried to write new ones. During this, we identified and solved important problems, such as site creation (adapting the code written by Davide Moro at the last Sorrento sprint), login and logout as different users (test suite layers). We also realized it is sometimes difficult to carry out the tests we want with Selenium.
  
• Sylvain Viollon worked on Funittest integration. After discussing the topic, we agreed that this method should live in parallel with the already existing one that uses prerecorded tests. Because of platform dependency problems and the challenge of the different testing models, the evaluation and adoption of Funittest might be a longer process. As a first step, Sylvain made a buildout that contains all package dependencies, and wrote example tests for Plone with the help of Massimo Azzolini. We also explored the possibility of converting Funittests testrun snapshots into a sequential format that can be played directly with Selenium IDE and thus used with the existing KSS testrunner.

We also looked into future possibilities. We started with the help of Robert Niederreiter the evaluaton of Cornerstone, the ajaxian widget framework of Devilstick. We definitely need more time to evaluate this component, and consider the possibility of adopting code and/or ideas for widget support into KSS.

Check out material

The documentation that explains how to install the test running environment, how to run the existing tests, and how to write new ones, can be found here. Check it out!:

The ploneout branch that enables selenium testing of Plone 3.1 is here:

https://svn.plone.org/svn/plone/ploneout/branches/3.1-kss-test

The kss.demo extensions are still subject to change, but you can simply drop new tests inside plone.app.kss, under the selenium_tests directory and they will be picked up automatically.

Funittest

The experimental Funittest integration buildout is here:

https://svn.plone.org/svn/plone/ploneout/branches/3.1-funittest

Actual tests are in funittest.plone, in the lib/plone/kss directory. More information on using Funittest is available on OpenPlans, together with more technical reports as well.