Comments on: Testing Wicket with Fitnesse http://blog.xebia.com/2008/07/06/testing-wicket-with-fitnesse/ Thu, 18 Mar 2010 13:27:36 +0100 http://wordpress.org/?v=2.8.4 hourly 1 By: Mischa Dasberg http://blog.xebia.com/2008/07/06/testing-wicket-with-fitnesse/comment-page-1/#comment-48144 Mischa Dasberg Wed, 23 Jul 2008 09:14:36 +0000 http://blog.xebia.com/?p=593#comment-48144 That's what we did. Before we submit we remove the feedbackmessages by calling a method clearErrorMessages() which does exactly what you said. We remove the feedbackmessages each time we submit, because we can submit multiple times using our Fitnesse fixture. That’s what we did.

Before we submit we remove the feedbackmessages by calling a method clearErrorMessages() which does exactly what you said. We remove the feedbackmessages each time we submit, because we can submit multiple times using our Fitnesse fixture.

]]> By: Carl http://blog.xebia.com/2008/07/06/testing-wicket-with-fitnesse/comment-page-1/#comment-48081 Carl Tue, 22 Jul 2008 15:00:43 +0000 http://blog.xebia.com/?p=593#comment-48081 We're been using Fitnesse and WicketTester for some time too. For the feed back we use getMessages on the BaseWicketTester rather than the FormTester. You just need to call Session.get().cleanupFeedbackMessages() after you have checked for the expected feedback. We’re been using Fitnesse and WicketTester for some time too.

For the feed back we use getMessages on the BaseWicketTester rather than the FormTester.

You just need to call Session.get().cleanupFeedbackMessages() after you have checked for the expected feedback.

]]> By: Mischa Dasberg http://blog.xebia.com/2008/07/06/testing-wicket-with-fitnesse/comment-page-1/#comment-47990 Mischa Dasberg Mon, 21 Jul 2008 11:04:27 +0000 http://blog.xebia.com/?p=593#comment-47990 Normally you will do something like this: formTester.select("markupId", position); What we wanted is that a tester can say: | select | role | with value | admin | and we will find the position of the role with that value, so the tester will know for sure that he selected the correct value. Normally you will do something like this:

formTester.select(”markupId”, position);

What we wanted is that a tester can say:

| select | role | with value | admin |

and we will find the position of the role with that value, so the tester will know for sure that he selected the correct value.

]]> By: Timo Rantalaiho http://blog.xebia.com/2008/07/06/testing-wicket-with-fitnesse/comment-page-1/#comment-47710 Timo Rantalaiho Fri, 18 Jul 2008 04:11:44 +0000 http://blog.xebia.com/?p=593#comment-47710 Thanks for the effort and sharing it! This is indeed interesting, I'll have a closer look on the WicketTester issues you mentioned, this already caught my attention: "Normally, using WicketTester you must define indexes for all fields that you want to test." What do you mean exactly? Also, you might be interested in looking at jdave-wicket ( http://www.jdave.org/ ) if you're interested in automatic Wicket testing. Some of the WicketTester issues that you mention also bite you there, but it makes it a bit easier to create descriptive tests (specs really) and offers some nice convenience utilities to use when testing Wicket. Cheers! Thanks for the effort and sharing it! This is indeed interesting, I’ll have a closer look on the WicketTester issues you mentioned, this already caught my attention:

“Normally, using WicketTester you must define indexes for all fields that you want to test.”

What do you mean exactly?

Also, you might be interested in looking at jdave-wicket ( http://www.jdave.org/ ) if you’re interested in automatic Wicket testing. Some of the WicketTester issues that you mention also bite you there, but it makes it a bit easier to create descriptive tests (specs really) and offers some nice convenience utilities to use when testing Wicket.

Cheers!

]]> By: Mischa Dasberg http://blog.xebia.com/2008/07/06/testing-wicket-with-fitnesse/comment-page-1/#comment-47427 Mischa Dasberg Sat, 12 Jul 2008 22:03:11 +0000 http://blog.xebia.com/?p=593#comment-47427 @Eelco, that would be great! @Eelco, that would be great!

]]> By: PY http://blog.xebia.com/2008/07/06/testing-wicket-with-fitnesse/comment-page-1/#comment-47049 PY Mon, 07 Jul 2008 21:47:40 +0000 http://blog.xebia.com/?p=593#comment-47049 Great article. But it places the fitnesse test on a "StutsTestCase" like level. What about an integration Fitnesse+Selenium for a global regression + functional testing? Advantage would be to test javascript and end-user experience as well. Great article.
But it places the fitnesse test on a “StutsTestCase” like level.
What about an integration Fitnesse+Selenium for a global regression + functional testing?
Advantage would be to test javascript and end-user experience as well.

]]> By: Eelco Hillenius http://blog.xebia.com/2008/07/06/testing-wicket-with-fitnesse/comment-page-1/#comment-46971 Eelco Hillenius Sun, 06 Jul 2008 20:39:44 +0000 http://blog.xebia.com/?p=593#comment-46971 Cool, thanks for writing up the article. One of the main focusses of Wicket 1.5 will be improved automatic testing. Your participation (in discussions, patches, etc) would be highly appreciated! :-) Cool, thanks for writing up the article.

One of the main focusses of Wicket 1.5 will be improved automatic testing. Your participation (in discussions, patches, etc) would be highly appreciated! :-)

]]>