Dear all,
Wicket page test 3.0.1 is now available. It now works with Wicket 7 (and
6.x) and can reliably wait for the loading of the response page.
It is a library allowing you to unit test your Wicket pages easily,
supporting AJAX and Javascript without changes to your pages.
It's avai
Thanks for sharing the information!
kind regards
Tobias
> Am 24.02.2015 um 07:08 schrieb Kent Tong :
>
> Dear all,
>
> Wicket page test 3.0.0 is now available. It now works with Wicket 6.x and
> Selenium 2. It is a library allowing you to unit test your Wicket pages
> ea
Dear all,
Wicket page test 3.0.0 is now available. It now works with Wicket 6.x and
Selenium 2. It is a library allowing you to unit test your Wicket pages
easily, supporting AJAX and Javascript without changes to your pages.
It's available from maven central. Check out the tutorial at
On Tue, Oct 23, 2012 at 10:59 AM, James Selvakumar wrote:
> Sorry if this is asked previously. Is it advisable to use a shared wicket
> tester across multiple unit tests?
>
I would not recommend that.
WicketTester keeps a reference to YourApplication which may keep
references to any services for
Sorry if this is asked previously. Is it advisable to use a shared wicket
tester across multiple unit tests?
On Tue, Oct 23, 2012 at 3:39 PM, Martin Grigorov wrote:
> On Tue, Oct 23, 2012 at 10:38 AM, James mCruncher
> wrote:
> > Should that call be made on "tearDown" or "tearDownClass"?
>
> It
On Tue, Oct 23, 2012 at 10:38 AM, James mCruncher wrote:
> Should that call be made on "tearDown" or "tearDownClass"?
It depends where WicketTester is initialized.
>
> On Mon, Oct 22, 2012 at 6:01 PM, Martin Grigorov wrote:
>
>> Call it and try again.
>>
>> On Mon, Oct 22, 2012 at 11:45 AM, Arun
Should that call be made on "tearDown" or "tearDownClass"?
On Mon, Oct 22, 2012 at 6:01 PM, Martin Grigorov wrote:
> Call it and try again.
>
> On Mon, Oct 22, 2012 at 11:45 AM, Arunachalam Sibisakkaravarthi
> wrote:
> > No, We don't call wicketTester.destroy() at the end of tests.
> >
> > On Mo
Call it and try again.
On Mon, Oct 22, 2012 at 11:45 AM, Arunachalam Sibisakkaravarthi
wrote:
> No, We don't call wicketTester.destroy() at the end of tests.
>
> On Mon, Oct 22, 2012 at 5:01 PM, Martin Grigorov wrote:
>
>> Hi,
>>
>> Do you call wicketTester.destroy() at the end of your tests ?
>>
No, We don't call wicketTester.destroy() at the end of tests.
On Mon, Oct 22, 2012 at 5:01 PM, Martin Grigorov wrote:
> Hi,
>
> Do you call wicketTester.destroy() at the end of your tests ?
>
> On Mon, Oct 22, 2012 at 9:10 AM, Arunachalam Sibisakkaravarthi
> wrote:
> > Hai,
> >
> > Here we are u
Hi,
Do you call wicketTester.destroy() at the end of your tests ?
On Mon, Oct 22, 2012 at 9:10 AM, Arunachalam Sibisakkaravarthi
wrote:
> Hai,
>
> Here we are using wicket 1.5.7.
>
> We have a simple test for each wicket page to assert rendering like this:
>
> WicketTester.assertRendered
Hai,
Here we are using wicket 1.5.7.
We have a simple test for each wicket page to assert rendering like this:
WicketTester.assertRenderedPage(Page.class);
In our module we have 52 tests w.r.t wicket pages.
It takes so long to run these tests.
Please give suggestion to improve test ca
Dear all,
Wicket page test 2.0.1 is now available. It now works with Wicket 1.5-M3.
It is a library allowing you to unit test your Wicket pages easily,
supporting AJAX and Javascript without changes to your pages.
Get it from maven as described in http://wicketpagetest.sourceforge.net
Dear all,
Wicket page test 2.0.0 is now available. It is the first version
that works with Wicket 1.5-M1 and onwards. It is a library allowing
you to unit test your Wicket pages easily, supporting AJAX and
Javascript without changes to your pages.
Get it from maven as described in http
Dear all,
Wicket page test 1.6.1 is now available. It is a library allowing
you to unit test your Wicket pages easily, supporting AJAX and
Javascript without changes to your pages.
This minor release contains the follow changes:
* Fixed issue 3043110[1].
* Fixed issue 3037392[2
Dear all,
Wicket page test 1.6 is now available. It is a library allowing
you to unit test your Wicket pages easily, supporting AJAX and
Javascript without changes to your pages.
This release contains the follow changes:
* Support manual testing: allow some things to be mocked, without
Dear all,
Wicket page test 1.5 is now available. It is a library allowing you
to unit test your Wicket pages easily, supporting AJAX and
Javascript without changes to your pages.
New features implemented in this version:
* Start the Selenium server automatically.
* Support JUnit4 in
Dear all,
Wicket page test 1.4 is now available. It is a library allowing you
to unit test your Wicket pages easily, supporting AJAX and
Javascript without changes to your pages.
New features implemented in this version:
* Provide a super easy way to locate a DOM element with the Wicket ID. For
2010/3/27 Kent Tong :
> Dear all,
>
> Wicket page test 1.3 is now available. It is a library allowing you
> to unit test your Wicket pages easily, supporting AJAX and
> Javascript without changes to your pages.
>
> New features implemented in this version:
>
> * Provid
Dear all,
Wicket page test 1.3 is now available. It is a library allowing you
to unit test your Wicket pages easily, supporting AJAX and
Javascript without changes to your pages.
New features implemented in this version:
* Provide a generic starter page to launch another page whose
Dear all,
Wicket page test allows you to unit test Wicket pages easily including
its AJAX functionality.
Major enhancements in 1.2 is that now you can wait for the completion
of Ajax easily, without writing any Javascript. For example, in a test
case, do something like:
WicketSelenium
Dear all,
wicket page test allows you to unit test Wicket pages including its
AJAX functionality.
Major enhancements in 1.1.0:
* It now supports Google Guice along with the existing support for
Spring (Thanks to our new member developer, Andy Chu).
* It is now organized in modules so that you
21 matches
Mail list logo
