Re: Re: Re: Re: Re: Basic JUnit Test

2012-08-28 Thread JCoder
What exactly do you mean by 'quickstart' ? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org

Re: Re: Re: Re: Basic JUnit Test

2012-08-27 Thread Martin Grigorov
A mini application that reproduces the problem. See http://wicket.apache.org/start/quickstart.html On Tue, Aug 28, 2012 at 8:21 AM, JCoder wrote: > What exactly do you mean by 'quickstart' ? > > - > To unsubscribe, e-mail: users-

Re: Re: Re: Re: Basic JUnit Test

2012-08-27 Thread JCoder
What exactly do you mean by 'quickstart' ? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org

Re: Re: Re: Basic JUnit Test

2012-08-20 Thread vineet semwal
that test looks ok to me ,please attach a quickstart On Mon, Aug 20, 2012 at 12:23 PM, JCoder wrote: > Hi Vineet, > > thanks for the reply. The line > "tester.getServletRequest().setParameter("myParam", "testParam");" > But now Im breaking my head with the next issue. If you look at my first >

Re: Re: Re: Basic JUnit Test

2012-08-19 Thread JCoder
Hi Vineet, thanks for the reply. The line "tester.getServletRequest().setParameter("myParam", "testParam");" But now Im breaking my head with the next issue. If you look at my first post, Im trying to do a test where a second page is rendered after a submit on an AjaxButton. The test code looks

Re: Re: Basic JUnit Test

2012-08-17 Thread vineet semwal
why are you attaching a new ajaxformsubmitbehavior to an ajaxbutton ,it already has it's own ? if you want to pass some request parameter ,you can set it to the request by tester.getRequest().setParameter(key,value) On Fri, Aug 17, 2012 at 12:09 PM, JCoder wrote: > Hi Vineet, > > "wickettester

Re: Re: Basic JUnit Test

2012-08-16 Thread JCoder
Hi Vineet, "wickettester#ajaxEvent(button,"onclick") " is what I already tried. And it worked better but not finally finsihed. The cause of the next problem is that I need to provide some request parameter for this request since my application reads request and throws an exception if it can't f

Re: Basic JUnit Test

2012-08-16 Thread vineet semwal
sorry typo i meant wickettester#executeAjaxEvent(button,"onclick") On Thu, Aug 16, 2012 at 8:11 PM, vineet semwal wrote: > that is expected behavior try > wickettester#ajaxEvent(button,"onclick") or it's path equivalent > > > On Thu, Aug 16, 2012 at 7:00 PM, JCoder wrote: >> Furthermore, I fou

Re: Basic JUnit Test

2012-08-16 Thread vineet semwal
that is expected behavior try wickettester#ajaxEvent(button,"onclick") or it's path equivalent On Thu, Aug 16, 2012 at 7:00 PM, JCoder wrote: > Furthermore, I found out that my test code calls "public void onSubmit();" > instead of calling the overridden "protected void onSubmit(AjaxRequestTar

Re: Basic JUnit Test

2012-08-16 Thread JCoder
Furthermore, I found out that my test code calls "public void onSubmit();" instead of calling the overridden "protected void onSubmit(AjaxRequestTarget target, Form form);" These overriden methods reside in my anonymous inner subclass of AjaxButton. --

Re: Basic JUnit Test

2012-08-16 Thread JCoder
Well it turns out that reflective call of a method failes. I run into WicketRuntimeException in RequestListenerInterface.invoke(Page, Component). The button to submit is an instance of AjaxButton. Does this make a difference in initializing the test? Regards, Y

RE: Basic JUnit Test

2012-08-13 Thread Paul Bors
[mailto:mgrigo...@apache.org] Sent: Monday, August 13, 2012 11:53 AM To: users@wicket.apache.org Subject: Re: Basic JUnit Test Hi, Put a breakpoint in the button's onSubmit() method and see whether it is actually called. It could be that you need to call formTester.submit("myForm:myButton");

Re: Basic JUnit Test

2012-08-13 Thread Martin Grigorov
Hi, Put a breakpoint in the button's onSubmit() method and see whether it is actually called. It could be that you need to call formTester.submit("myForm:myButton"); On Mon, Aug 13, 2012 at 5:18 PM, JCoder wrote: > Hi all, > > Im working at a basic Unit Test that looks like this: > > 1. tester.a