I have created a new page with link and then execute:
DummyBasePage page = new DummyBasePage(action);
startPage(page);
clickLink(page.getActionLink());
where action link is a link to another page.
But it is still not working, only DummyBasePage is rendered. Then I look
into
I have looked inside 1.4 and the code inside a clickLink() is very similar,
so this is not a case to 6.x. But still it would be nice to have
RequestCycle#setResponsePage() working ;).
--
Daniel
On Thu, Feb 6, 2014 at 10:00 AM, Daniel Stoch daniel.st...@gmail.comwrote:
I have created a new
I am actually wondering how to hide this API from the developer in the
tests.
The idea of the tester is to simulate sending requests to the
pages/resources.
tester.getRequestCycle().setResponsePage() doesn't test anything in the
application.
tester.getRequestCycle().setResponsePage() is like to
If you see any regressions in WicketTester since 1.4.x/1.5.x please report
ticket with a test case.
I believe it is even much more powerful than in 1.4.x but since there was
redesign of WicketTester in 1.5.0 there could be regressions.
Martin Grigorov
Wicket Training and Consulting
On Thu, Feb
Try with tester.setExposeExceptions(false) before making the request to the
secured page
Martin Grigorov
Wicket Training and Consulting
On Wed, Feb 5, 2014 at 10:33 AM, Daniel Stoch daniel.st...@gmail.comwrote:
Hi,
I'm during migration from Wicket 1.4.x to 6.x and I have the following
It works!
Thanks for your fast replay :)
--
Daniel
On Wed, Feb 5, 2014 at 10:40 AM, Martin Grigorov mgrigo...@apache.orgwrote:
Try with tester.setExposeExceptions(false) before making the request to the
secured page
Martin Grigorov
Wicket Training and Consulting
On Wed, Feb 5, 2014 at
For fast REPLY, of course ;)
On Wed, Feb 5, 2014 at 10:45 AM, Daniel Stoch daniel.st...@gmail.comwrote:
It works!
Thanks for your fast replay :)
--
Daniel
On Wed, Feb 5, 2014 at 10:40 AM, Martin Grigorov mgrigo...@apache.orgwrote:
Try with tester.setExposeExceptions(false) before
One more question: what is a difference between these two calls:
1.
tester.startPage(DummyBasePage.class);
Result result = tester.isRenderedPage(DummyBasePage.class);
2.
tester.getRequestCycle().setResponsePage(DummyBasePage.class);
tester.processRequest();
Result result =
#processRequest() triggers a new request to the server
so first the page is rendered, then a new request to the default
destination is made, so the home page is rendered and lastRenderedPage
changes
Martin Grigorov
Wicket Training and Consulting
On Wed, Feb 5, 2014 at 11:39 AM, Daniel Stoch
Ok, but what I should call to render DummyBasePage after calling:
tester.getRequestCycle().setResponsePage(DummyBasePage.class);
without making a new request?
--
Daniel
On Wed, Feb 5, 2014 at 12:01 PM, Martin Grigorov mgrigo...@apache.orgwrote:
#processRequest() triggers a new request to
You should not use tester.getRequestCycle().setResponsePage(DummyBasePage.
class);
You should do something like:
- in the test code: tester.startPage(Page1.class)
- in your real application code: Page1 or in its components you can use
setResponsePage(Page2.class)
- finally in the test code:
In my real application there are calls to RequestCycle.setResponsePage(...)
which are hidden by more advanced action/navigation framework. So I cannot
simply replace them by component.setResponsePage().
I think that if RequestCycle.setResponsePage(...) is valid for real
application, it should also
Component#setResponsePage() just delegates to
RequestCycle#setResponsePage(). So it is the same.
I'm saying that you should not use tester.getRequestCycle().xyz(). I.e. do
not set the new page in the test code. Set it in the real application code.
Martin Grigorov
Wicket Training and Consulting
13 matches
Mail list logo
