[Hippo-cms7-user] Automatic testing not possible with dynamic id's in CMS7

Jeroen Reijn j.reijn at onehippo.com
Tue Aug 4 09:41:33 CEST 2009

Might be good to share some more information on this subject.

Even though this patch sounds useful, I've tried it a couple of times, 
but it only works if you test in a certain way.

At a project that I'm currently working on, we tried the wicket patch, 
but this will only work if you deploy the CMS/Repository application and 
perform all you test after the first login.

We wrote some test that would login and logout with different users that 
would perform different actions. In this case the ids do change after 
logout and login again, so this was not a working situation for us.

Perhaps this was the case, because we deployed the CMS to an external 
app server and performed our tests there, instead of redeploying the app 
with every test.



Arthur Bogaart wrote:
> Hi Sander,
> You can read a blog post about how to set this up 
> here: http://blogs.hippo.nl/arthur/2009/02/hippoecm_integration_testing_w.html
> Also you can read the documentation about how to set your environment up 
> correctly here: http://www.onehippo.org/cms7/integration_testing.html
> Regards,
> Arthur Bogaart
> 2009/7/21 Berry van Halderen <b.vanhalderen at onehippo.com 
> <mailto:b.vanhalderen at onehippo.com>>
>     On Tue, Jul 21, 2009 at 4:33 PM, Sander Martens<SMartens at iprofs.nl
>     <mailto:SMartens at iprofs.nl>> wrote:
>      > Because the new CMS7 is using wicket generated ID's, all our
>     automatic tests
>      > fail when played back.
>      > For example, when navigating through the folder tree a button
>     pops up. If
>      > you click this button a menu appears which gives you the
>     possibility to
>      > create a new document. All the test tools we've used, don't have
>     a 'hook' to
>      > this button. Its name always changes from wicket-generated-id-27
>     in the
>      > current session to e.g. wicket-generated-id-56 in the next session.
>      > Recording a testscript is possible but playback is almost never
>     possible.
>      > The tools (selenium, badboy, sahi, etc.)  simply don't recognise
>     the button
>      > anymore.
>     Yes indeed, the generated wicket ids form a problem.  Indeed, it is
>     possible
>     to test the CMS with selenium, and we've made provisions for this in
>     the CMS,
>     but still this requires stable wicket ids.  These can be generated
>     stable, but in
>     order to do this you have to use a patched wicket version.
>     The patch is available in our source tree (of Hippo ECM) in the file:
>      tools/testutils/wicket-selenium.patch
>     A patch for this has been submitted to wicket, and its basic
>     principle has been
>     okayed, but never made it to any release.
>     \Berry
>     _______________________________________________
>     Hippo-cms7-user mailing list and forums
>     http://www.onehippo.org/cms7/support/community.html
> -- 
> Kind regards,
> Met vriendelijke groet,
> Arthur Bogaart
> Hippo
> a.bogaart at onehippo.com <mailto:a.bogaart at onehippo.com>
> Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
> San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 
> 94952-3329 +1 (707) 773-4646
> www.onehippo.com <http://www.onehippo.com> info at onehippo.com 
> <mailto:info at onehippo.com>
> ------------------------------------------------------------------------
> _______________________________________________
> Hippo-cms7-user mailing list and forums
> http://www.onehippo.org/cms7/support/community.html

More information about the Hippo-cms7-user mailing list