> However, I already had tested this and it doesn't make any difference -
> the test still fails with the same error.

I am not sure what you are doing. Do like this

{
  // Operation 1
  FormTester f1 = tester.newFormTester (...);
  f1.setValue....
  tester.execute ...
}

{
  // Operation 2
  FormTester f1 = tester.newFormTester (...);
  f1.setValue....
  f1.submit
}


**
Martin

>
> Thanx && cheers,
> Martin
>
>
>>
>> **
>> Martin
>>
>> 2009/12/1 Martin Grotzke <martin.grot...@javakaffee.de>:
>> > On Tue, 2009-12-01 at 11:44 +0200, Martin Makundi wrote:
>> >> > Thanx for your feedback! Did you have a look at http://is.gd/58mq3 which
>> >> > shows the test?
>> >>
>> >> Ofcourse I didn't look ;)
>> >>
>> >> Now, having looked at it your bug is that FORMTESTER CAN BE SUBMITTED 
>> >> ONLY ONCE!
>> >>
>> >> If you want to use it another time, you need to call newFormTester again.
>> > Thanx, this fixed the issue!
>> >
>> > Now I extended the test to make sure that the previously selected make
>> > and model are still selected after the final submit - and this fails
>> > with the second drop down (the model): this returns null from
>> > dropDown.getDefaultModelObject. I pushed this, so http://is.gd/58mq3
>> > shows these changes.
>> >
>> > Is there another thing that needs to be changed in the test?
>> >
>> > Cheers,
>> > Martin
>> >
>> >
>> >>
>> >> **
>> >> Martin
>> >> >
>> >> >
>> >> >>
>> >> >> **
>> >> >> Martin
>> >> >>
>> >> >> >
>> >> >> > This issue was already reported some time ago without a final result:
>> >> >> > http://old.nabble.com/unit-test-for-dropdownchoice-with-ajax-td21141772.html
>> >> >> >
>> >> >> >
>> >> >> > I created an example project that shows this issue:
>> >> >> > http://github.com/magro/misc/tree/master/wicket-tester-drop-downs/
>> >> >> >
>> >> >> > This is the short link to the failing test case (on github): 
>> >> >> > http://is.gd/58mq3
>> >> >> > This is the tested page class: http://is.gd/58mDm
>> >> >> >
>> >> >> > I'm using wicket 1.4.3.
>> >> >> >
>> >> >> > Is there any error in the test? Can I do anything to work around 
>> >> >> > this,
>> >> >> > or is it a bug?
>> >> >> >
>> >> >> > Thanx && cheers,
>> >> >> > Martin
>> >> >> >
>> >> >> > --
>> >> >> > Martin Grotzke
>> >> >> > http://www.javakaffee.de/blog/
>> >> >> >
>> >> >>
>> >> >> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> >> >> For additional commands, e-mail: users-h...@wicket.apache.org
>> >> >>
>> >> > --
>> >> > Martin Grotzke
>> >> > http://www.javakaffee.de/blog/
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> >> For additional commands, e-mail: users-h...@wicket.apache.org
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to