On 29 November 2012 08:03, Martin Grigorov <[email protected]> wrote:
> Hi Anatoly, > > You are doing it right. > To be able to verify that the other page is the response this other page > have to be properly rendered, otherwise you would receive InternalErrorPage > instead. > To render it Wicket uses the normal rendering process so you need all > prerequisites ... > Yes, exactly. I've tried to mock/spy RequestCycle object to verify setResponsePage calls, however no success, too many dependencies. > You can use tester#startComponentInPage() to test on component level. But > this is not what you need. > Not sure how could it help me. My aim is to verify that a link on a page follows to another page if some conditions are met. startComponent doesn't deal with pages, and also assumes use of clickLink. What's a difference? -- WBR, Anatoly.
