[
https://issues.apache.org/jira/browse/WICKET-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Rantalaiho updated WICKET-1214:
------------------------------------
Fix Version/s: (was: 1.4-M4)
1.5-M1
Assignee: Timo Rantalaiho
Currently, you can do
WicketTester tester = new WicketTester();
tester.startPanel(HelloWorldPanel.class);
tester.assertLabel(DummyPanelPage.TEST_PANEL_ID + ":message", "Hello, World!");
or with jdave-wicket
specify(selectFirst(Label.class,
"message").from(context).getModelObjectAsString(), does.equal("Hello, World"));
(or something similar with direct IVisitor usage and JUnit ) and I don't think
it makes sense to make it any better in 1.4.
Let's hope that we can improve testing in 1.5! Meanwhile, jdave-wicket is worth
checking out if you are into test-/behavior-driving or unit testing Wicket
components.
> WicketTester#startPanel does not work (correctly)
> -------------------------------------------------
>
> Key: WICKET-1214
> URL: https://issues.apache.org/jira/browse/WICKET-1214
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.4-M1
> Reporter: Martijn Dashorst
> Assignee: Timo Rantalaiho
> Fix For: 1.5-M1
>
>
> WicketTester#startPanel(class<? extends Panel>) does not work with the
> assertions:
> WicketTester tester = new WicketTester();
> tester.startPanel(HelloWorldPanel.class);
> tester.assertLabel("message", "Hello, World!");
> Will throw an exception because "message" can't be found. In the response
> page the panel is added with component identifier "panel". However as a
> tester I expect to be able to assert the components directly without having
> to know what happens internally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
