[Kss-devel] KSS & tests

[Jeroen Vloothuis]

Florian Kamm wrote:
> at the moment I am working on doctests and functionality tests for
> my KSS-based batching product (btw it has been checked in into the
> collective repository in the meantime).  To get used on testing
> KSS-based products I looked into the plone.app.kss , kss.core and
> kss.demo code base of plone 3.0 trunk, but I am a little bit confused
> now. What is the preferred way of testing KSS-products? 
>   
The prefered way of testing I think you will want to test at multiple
levels. One of the easiest ways to avoid breaking KSS functionality is
checking for classes and id's in your template output. You can do this
by writing functional test browser tests (zope.testbrowser). These of
course don't test the actual javascript.

If you only use KSS as an end user then this should be enough (depending
on your trust in the framework).

When you write you're own plugins or want to do full testing of your app
then selenium is the way to go.
> And is the
> selenium rc approach the one and only way of functionality testing (saw
> it in the demo package)? It would be nice to get some help from you
> regarding these topics...
>   
To the KSS framework itself selenium is used. Because testing different
platforms is tedious automation using selenium rc is key. There is
already quite some work done to make automated tests for KSS a reality.
One of the components in this is the kss.demo package. This exercises
core framework functionality (so that it is testable by selenium).

Cheers,
    Jeroen