On 3/2/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
All the components are logged as 'not rendered', but all tests are
passed and the application works.
Is this the normal behaviour of tests?
That doesn't look normal to me. Did you get any further insight?
Yes, what I discovered is that
So, you're using Wicket 1.2.5?
I came across the same thing, and had to disable a unit test:
See bugTestPageConstructor() in WicketTesterTest
And like you it uses the startPage(Page) method.
What is really strange is that the same code runs smoothly in
Wicket 2. Help from the team would
On 3/4/07, Jean-Baptiste Quenot [EMAIL PROTECTED] wrote:
So, you're using Wicket 1.2.5?
Yes, Wicket 1.2.5
--
Filippo Diotalevi
http://www.diotalevi.com
http://www.jugmilano.it
-
Take Surveys. Earn Cash. Influence the
All the components are logged as 'not rendered', but all tests are
passed and the application works.
Is this the normal behaviour of tests?
That doesn't look normal to me. Did you get any further insight?
Eelco
-
Take
Hi,
I'm writing tests using WicketTester (with Wicket 1.2.5); a sample test is:
public void testPageShouldHaveRequiredComponents() {
WicketTester wt = new WicketTester();
wt.startPage(new
SummaryPage(JobPostCreatorHelper.createJobPost()));
