[Hippo-cms7-user] Automatic testing not possible with dynamic id's in CMS7
gerritberkouwer at gmail.com
Wed Aug 19 18:02:47 CEST 2009
What I was afraid of now happened: this problem is officially lost in
4-1/2 weeks ago this thread started, and there is no solution to this
Any ideas anyone? For our project this becomes a major drawback. I need some
serious solution-making from anyone, anywhere...
Berry van Halderen wrote:
> On Wed, Aug 12, 2009 at 9:34 AM, Maurizio
> Pillitu<m.pillitu at sourcesense.com> wrote:
>> super! Looking forward to try it!
>> Regarding the patched wicket jar, wouldn't be cleaner to exclude the
>> wicket dependency and include the patched one using maven? Maybe using a
>> test profile?
> Is also possible, this way you can transparently switch without
> re-compiling the target. Actually, I would like the patch, or some
> form of it, to go into Wicket, but it keeps getting postponed.
>> Berry van Halderen <b.vanhalderen at onehippo.com> wrote:
>>>Good to see that so many people are trying out the automated testing.
>>>This is a good thing.
>>>I tried the unit test a number of times, and I've committed a new
>>>Selenium based unit test specifically for the trunk of the development
>>>of the CMS. If I try those. I can run this test without any real
>>>To make it easier, we've pre-prepared the patched wicket, at put it on
>>>a location you can download:
>>>Get the wicket-1.3.5.jar file and put it in your local machine maven
>>> mvn deploy:deploy-file -Dfile=wicket-1.3.5.jar
>>>-DgroupId=org.apache.wicket -DartifactId=wicket -Dversion=1.3.5
>>>Then checkout the HippoECM trunk
>>> svn checkout http://svn.onehippo.org/repos/hippo/hippo-ecm/trunk
>>> cd hippo-ecm ; mvn install
>>>And you can then run the unit test. There is a small test script
>>>which runs the SmokeTest on the trunk. I've attached the test script,
>>>you'll have to modify the paths.
>>>Now I've think you've already gotten this far. But still you find the
>>>tests not working. Which limitation are the actual problem. It's
>>>hard to find out with a complete test, but when running a test you can
>>>put selenium in a "slow" mode (there is a check box), so you can
>>>actually see the step failing you assume that should work. Which one
>>>does it seem to be then?
>>>Apart from Arthurs blog I've written a piece of documentation on unit
>>>testing, not directly accessible from the documentation web-site. You
>>>can still read it:
>>>With kind regards,
>>>Berry van Halderen
>>>Hippo-cms7-user mailing list and forums
>> Hippo-cms7-user mailing list and forums
> Hippo-cms7-user mailing list and forums
View this message in context: http://n2.nabble.com/Automatic-testing-not-possible-with-dynamic-id%27s-in-CMS7-tp3299348p3473362.html
Sent from the Hippo CMS 7 mailing list archive at Nabble.com.
More information about the Hippo-cms7-user