You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martijn Dashorst (JIRA)" <ji...@apache.org> on 2007/12/09 17:09:43 UTC
[jira] Created: (WICKET-1214) WicketTester#startPanel does not work
(correctly)
WicketTester#startPanel does not work (correctly)
-------------------------------------------------
Key: WICKET-1214
URL: https://issues.apache.org/jira/browse/WICKET-1214
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.3.0-rc1
Reporter: Martijn Dashorst
Fix For: 1.3.0-rc3
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.
[jira] Updated: (WICKET-1214) WicketTester#startPanel does not work
(correctly)
Posted by "Martijn Dashorst (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martijn Dashorst updated WICKET-1214:
-------------------------------------
Affects Version/s: (was: 1.3.0-final)
1.4-M1
> WicketTester#startPanel does not work (correctly)
> -------------------------------------------------
>
> Key: WICKET-1214
> URL: https://issues.apache.org/jira/browse/WICKET-1214
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4-M1
> Reporter: Martijn Dashorst
> Fix For: 1.4-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.
[jira] Updated: (WICKET-1214) WicketTester#startPanel does not work
(correctly)
Posted by "Timo Rantalaiho (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (WICKET-1214) WicketTester#startPanel does not work
(correctly)
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg updated WICKET-1214:
----------------------------------
Fix Version/s: 1.5-M3
(was: 1.5-M2)
> 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: Juergen Donnerstag
> Fix For: 1.5-M3
>
>
> 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.
[jira] Updated: (WICKET-1214) WicketTester#startPanel does not work
(correctly)
Posted by "Frank Bille Jensen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Bille Jensen updated WICKET-1214:
---------------------------------------
Fix Version/s: (was: 1.4-M1)
1.4-M2
> 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
> Fix For: 1.4-M2
>
>
> 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.
[jira] Updated: (WICKET-1214) WicketTester#startPanel does not work
(correctly)
Posted by "Martijn Dashorst (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martijn Dashorst updated WICKET-1214:
-------------------------------------
Affects Version/s: (was: 1.3.0-rc1)
1.3.0-final
Fix Version/s: (was: 1.3.1)
1.4-M1
Moved to 1.4, as we will look at the wicket tester for a make over.
> WicketTester#startPanel does not work (correctly)
> -------------------------------------------------
>
> Key: WICKET-1214
> URL: https://issues.apache.org/jira/browse/WICKET-1214
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4-M1
> Reporter: Martijn Dashorst
> Fix For: 1.4-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.
[jira] Updated: (WICKET-1214) WicketTester#startPanel does not work
(correctly)
Posted by "Frank Bille Jensen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Bille Jensen updated WICKET-1214:
---------------------------------------
Fix Version/s: (was: 1.3.0-rc3)
1.3.1
> WicketTester#startPanel does not work (correctly)
> -------------------------------------------------
>
> Key: WICKET-1214
> URL: https://issues.apache.org/jira/browse/WICKET-1214
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-rc1
> Reporter: Martijn Dashorst
> Fix For: 1.3.1
>
>
> 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.
[jira] Assigned: (WICKET-1214) WicketTester#startPanel does not
work (correctly)
Posted by "Juergen Donnerstag (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juergen Donnerstag reassigned WICKET-1214:
------------------------------------------
Assignee: Juergen Donnerstag (was: Timo Rantalaiho)
> 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: Juergen Donnerstag
> 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.
[jira] Updated: (WICKET-1214) WicketTester#startPanel does not work
(correctly)
Posted by "Jeremy Thomerson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Thomerson updated WICKET-1214:
-------------------------------------
Fix Version/s: (was: 1.5-M3)
1.5-M4
> 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: Juergen Donnerstag
> Fix For: 1.5-M4
>
>
> 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.
[jira] Updated: (WICKET-1214) WicketTester#startPanel does not work
(correctly)
Posted by "Frank Bille Jensen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Bille Jensen updated WICKET-1214:
---------------------------------------
Fix Version/s: (was: 1.4-M2)
1.4-M3
> 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
> Fix For: 1.4-M3
>
>
> 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.
[jira] Updated: (WICKET-1214) WicketTester#startPanel does not work
(correctly)
Posted by "Martijn Dashorst (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martijn Dashorst updated WICKET-1214:
-------------------------------------
Issue Type: Improvement (was: Bug)
> 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
> Fix For: 1.4-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.
[jira] Updated: (WICKET-1214) WicketTester#startPanel does not work
(correctly)
Posted by "Martijn Dashorst (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martijn Dashorst updated WICKET-1214:
-------------------------------------
Fix Version/s: (was: 1.4-M3)
1.4-M4
Moved to next milestone release.
> 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
> Fix For: 1.4-M4
>
>
> 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.
[jira] Updated: (WICKET-1214) WicketTester#startPanel does not work
(correctly)
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg updated WICKET-1214:
----------------------------------
Fix Version/s: 1.5-M2
(was: 1.5-M1)
> 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: Juergen Donnerstag
> Fix For: 1.5-M2
>
>
> 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.