Wicket page test 3.0.1 is now available (for Wicket 7.0 and 6.x)

2015-08-26 Thread Kent Tong
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 available from maven central. Check out the tutorial at
http://wicketpagetest.sourceforge.net to get started!

-- 
Kent Tong
IT author and consultant, child education coach


Wicket page test 3.0.0 is now available (for Wicket 6.x)

2015-02-23 Thread 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
easily, supporting AJAX and Javascript without changes to your pages.

It's available from maven central. Check out the tutorial at
http://wicketpagetest.sourceforge.net to get started!

-- 
Kent Tong
IT author and consultant, TipTec Development


Re: Wicket page test 3.0.0 is now available (for Wicket 6.x)

2015-02-23 Thread Tobias Soloschenko
Thanks for sharing the information!

kind regards

Tobias

 Am 24.02.2015 um 07:08 schrieb Kent Tong kent.tong...@gmail.com:
 
 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
 http://wicketpagetest.sourceforge.net to get started!
 
 -- 
 Kent Tong
 IT author and consultant, TipTec Development

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Wicket page test

2012-10-23 Thread James mCruncher
Should that call be made on tearDown or tearDownClass?

On Mon, Oct 22, 2012 at 6:01 PM, Martin Grigorov mgrigo...@apache.orgwrote:

 Call it and try again.

 On Mon, Oct 22, 2012 at 11:45 AM, Arunachalam Sibisakkaravarthi
 arunacha...@mcruncher.com wrote:
  No, We don't call wicketTester.destroy() at the end of tests.
 
  On Mon, Oct 22, 2012 at 5:01 PM, Martin Grigorov mgrigo...@apache.org
 wrote:
 
  Hi,
 
  Do you call wicketTester.destroy() at the end of your tests ?
 
  On Mon, Oct 22, 2012 at 9:10 AM, Arunachalam Sibisakkaravarthi
  arunacha...@mcruncher.com 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.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 cases that how to reduce the
 time
   taken by this module.
  
   --
   *Thanks And Regards
   Sibi.Arunachalam
   mCruncher*
 
 
 
  --
  Martin Grigorov
  jWeekend
  Training, Consulting, Development
  http://jWeekend.com
 
  -
  To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
  For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 
 
  --
  *Thanks And Regards
  Sibi.Arunachalam
  mCruncher*



 --
 Martin Grigorov
 jWeekend
 Training, Consulting, Development
 http://jWeekend.com

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




-- 
Thanks  regards
James Selvakumar


Re: Wicket page test

2012-10-23 Thread Martin Grigorov
On Tue, Oct 23, 2012 at 10:38 AM, James mCruncher ja...@mcruncher.com 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 mgrigo...@apache.orgwrote:

 Call it and try again.

 On Mon, Oct 22, 2012 at 11:45 AM, Arunachalam Sibisakkaravarthi
 arunacha...@mcruncher.com wrote:
  No, We don't call wicketTester.destroy() at the end of tests.
 
  On Mon, Oct 22, 2012 at 5:01 PM, Martin Grigorov mgrigo...@apache.org
 wrote:
 
  Hi,
 
  Do you call wicketTester.destroy() at the end of your tests ?
 
  On Mon, Oct 22, 2012 at 9:10 AM, Arunachalam Sibisakkaravarthi
  arunacha...@mcruncher.com 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.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 cases that how to reduce the
 time
   taken by this module.
  
   --
   *Thanks And Regards
   Sibi.Arunachalam
   mCruncher*
 
 
 
  --
  Martin Grigorov
  jWeekend
  Training, Consulting, Development
  http://jWeekend.com
 
  -
  To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
  For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 
 
  --
  *Thanks And Regards
  Sibi.Arunachalam
  mCruncher*



 --
 Martin Grigorov
 jWeekend
 Training, Consulting, Development
 http://jWeekend.com

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




 --
 Thanks  regards
 James Selvakumar



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Wicket page test

2012-10-23 Thread James Selvakumar
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 mgrigo...@apache.orgwrote:

 On Tue, Oct 23, 2012 at 10:38 AM, James mCruncher ja...@mcruncher.com
 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 mgrigo...@apache.org
 wrote:
 
  Call it and try again.
 
  On Mon, Oct 22, 2012 at 11:45 AM, Arunachalam Sibisakkaravarthi
  arunacha...@mcruncher.com wrote:
   No, We don't call wicketTester.destroy() at the end of tests.
  
   On Mon, Oct 22, 2012 at 5:01 PM, Martin Grigorov 
 mgrigo...@apache.org
  wrote:
  
   Hi,
  
   Do you call wicketTester.destroy() at the end of your tests ?
  
   On Mon, Oct 22, 2012 at 9:10 AM, Arunachalam Sibisakkaravarthi
   arunacha...@mcruncher.com 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.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 cases that how to reduce the
  time
taken by this module.
   
--
*Thanks And Regards
Sibi.Arunachalam
mCruncher*
  
  
  
   --
   Martin Grigorov
   jWeekend
   Training, Consulting, Development
   http://jWeekend.com
  
   -
   To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
   For additional commands, e-mail: users-h...@wicket.apache.org
  
  
  
  
   --
   *Thanks And Regards
   Sibi.Arunachalam
   mCruncher*
 
 
 
  --
  Martin Grigorov
  jWeekend
  Training, Consulting, Development
  http://jWeekend.com
 
  -
  To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
  For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 
 
  --
  Thanks  regards
  James Selvakumar



 --
 Martin Grigorov
 jWeekend
 Training, Consulting, Development
 http://jWeekend.com

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




-- 
Thanks  regards
James Selvakumar


Re: Wicket page test

2012-10-23 Thread Martin Grigorov
On Tue, Oct 23, 2012 at 10:59 AM, James Selvakumar ja...@mcruncher.com 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 your app.
By keeping reusing the same WicketTester you should make sure that all
your services are reusable, i.e. do not keep state.

 On Tue, Oct 23, 2012 at 3:39 PM, Martin Grigorov mgrigo...@apache.orgwrote:

 On Tue, Oct 23, 2012 at 10:38 AM, James mCruncher ja...@mcruncher.com
 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 mgrigo...@apache.org
 wrote:
 
  Call it and try again.
 
  On Mon, Oct 22, 2012 at 11:45 AM, Arunachalam Sibisakkaravarthi
  arunacha...@mcruncher.com wrote:
   No, We don't call wicketTester.destroy() at the end of tests.
  
   On Mon, Oct 22, 2012 at 5:01 PM, Martin Grigorov 
 mgrigo...@apache.org
  wrote:
  
   Hi,
  
   Do you call wicketTester.destroy() at the end of your tests ?
  
   On Mon, Oct 22, 2012 at 9:10 AM, Arunachalam Sibisakkaravarthi
   arunacha...@mcruncher.com 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.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 cases that how to reduce the
  time
taken by this module.
   
--
*Thanks And Regards
Sibi.Arunachalam
mCruncher*
  
  
  
   --
   Martin Grigorov
   jWeekend
   Training, Consulting, Development
   http://jWeekend.com
  
   -
   To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
   For additional commands, e-mail: users-h...@wicket.apache.org
  
  
  
  
   --
   *Thanks And Regards
   Sibi.Arunachalam
   mCruncher*
 
 
 
  --
  Martin Grigorov
  jWeekend
  Training, Consulting, Development
  http://jWeekend.com
 
  -
  To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
  For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 
 
  --
  Thanks  regards
  James Selvakumar



 --
 Martin Grigorov
 jWeekend
 Training, Consulting, Development
 http://jWeekend.com

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




 --
 Thanks  regards
 James Selvakumar



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Wicket page test

2012-10-22 Thread Arunachalam Sibisakkaravarthi
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 cases that how to reduce the time
taken by this module.

-- 
*Thanks And Regards
Sibi.Arunachalam
mCruncher*


Re: Wicket page test

2012-10-22 Thread Martin Grigorov
Hi,

Do you call wicketTester.destroy() at the end of your tests ?

On Mon, Oct 22, 2012 at 9:10 AM, Arunachalam Sibisakkaravarthi
arunacha...@mcruncher.com 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.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 cases that how to reduce the time
 taken by this module.

 --
 *Thanks And Regards
 Sibi.Arunachalam
 mCruncher*



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Wicket page test

2012-10-22 Thread Arunachalam Sibisakkaravarthi
No, We don't call wicketTester.destroy() at the end of tests.

On Mon, Oct 22, 2012 at 5:01 PM, Martin Grigorov mgrigo...@apache.orgwrote:

 Hi,

 Do you call wicketTester.destroy() at the end of your tests ?

 On Mon, Oct 22, 2012 at 9:10 AM, Arunachalam Sibisakkaravarthi
 arunacha...@mcruncher.com 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.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 cases that how to reduce the time
  taken by this module.
 
  --
  *Thanks And Regards
  Sibi.Arunachalam
  mCruncher*



 --
 Martin Grigorov
 jWeekend
 Training, Consulting, Development
 http://jWeekend.com

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




-- 
*Thanks And Regards
Sibi.Arunachalam
mCruncher*


Re: Wicket page test

2012-10-22 Thread Martin Grigorov
Call it and try again.

On Mon, Oct 22, 2012 at 11:45 AM, Arunachalam Sibisakkaravarthi
arunacha...@mcruncher.com wrote:
 No, We don't call wicketTester.destroy() at the end of tests.

 On Mon, Oct 22, 2012 at 5:01 PM, Martin Grigorov mgrigo...@apache.orgwrote:

 Hi,

 Do you call wicketTester.destroy() at the end of your tests ?

 On Mon, Oct 22, 2012 at 9:10 AM, Arunachalam Sibisakkaravarthi
 arunacha...@mcruncher.com 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.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 cases that how to reduce the time
  taken by this module.
 
  --
  *Thanks And Regards
  Sibi.Arunachalam
  mCruncher*



 --
 Martin Grigorov
 jWeekend
 Training, Consulting, Development
 http://jWeekend.com

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org




 --
 *Thanks And Regards
 Sibi.Arunachalam
 mCruncher*



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Wicket page test 2.0.0 is now available (for Wicket 1.5)

2010-08-14 Thread Kent Tong
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://wicketpagetest.sourceforge.net/


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Wicket page test 1.6.1 is now available

2010-08-11 Thread Kent Tong
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].
* Fixed issue 3037395[3].

Get it from maven as described in http://wicketpagetest.sourceforge.net/



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Wicket page test 1.6 is now available

2010-07-10 Thread Kent Tong
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
starting Selenium.
* Include a factory to create change-resisting mocks.
* Fixed issue 3024401[1].
* Fixed issue 3008847[2].
* Fixed issue 3008846[3]. That is, now it works with Wicket 1.4.9.

Get it from maven as described in http://wicketpagetest.sourceforge.net/



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Wicket page test 1.5 is now available

2010-05-15 Thread Kent Tong
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 addition to TestNG.
* Support unit testing the navigation within the Breadcrumb subsystem
* Open a Component in a page for unit testing
* Fixed issue 2998400.

Get it from maven as described in http://wicketpagetest.sourceforge.net/


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Wicket page test 1.4 is now available

2010-04-30 Thread Kent Tong
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
example, to locate the input element generated by a TextField with
wicket:id=productName, just use wicket=//productName as the locator. To
locate such element in the 3rd form with wicket:id=myForm, use
wicket=//myForm[3]//productName.

Get it from maven as described in http://wicketpagetest.sourceforge.net/



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Wicket page test 1.3 is now available

2010-03-27 Thread Martin Makundi
If you want to compose test pages on the fly, you should try also
mashupwebpage:

public void testSomeFieldComponent() {
 Page page = new MashupWebPage();
 Form form;
 page.add(form = new MashUpForm(GID));
 FormComponent customField;
 form.add(customField = new CustomFieldToBeTested(GID));
 tester.startPage(page);
 FormTester formtester = tester.newFormTester(form.getPageRelativePath());
 formtester.setValue(getRelativePath(form, customField), test-value);
 formtester.submit();
 tester.assertNoErrorMessages();
}

http://code.google.com/p/wicket-mashup/

**
Martin

2010/3/27 Kent Tong k...@cpttm.org.mo:
 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
 constructor needs some arguments.
    * Provide a page navigator to inspect the arguments passed to the
 response page.
    * Easier way to open a page.

 Get it from maven as described in http://wicketpagetest.sourceforge.net/

 --
 Author of books for learning CXF, Axis2, Wicket, JSF
 (http://www.agileskills2.org)


 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Wicket page test 1.3 is now available

2010-03-26 Thread 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:

* Provide a generic starter page to launch another page whose
constructor needs some arguments.
* Provide a page navigator to inspect the arguments passed to the
response page.
* Easier way to open a page.

Get it from maven as described in http://wicketpagetest.sourceforge.net/

--
Author of books for learning CXF, Axis2, Wicket, JSF
(http://www.agileskills2.org)


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Announce: wicket page test 1.2 is now available

2010-03-06 Thread Kent Tong

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 ws = new WicketSelenium(selenium);
selenium.click(link=Calculate next); //this is an ajax link
ws.waitUntilAjaxDone();
assert selenium.getText(output).equals(Current: 1);

For more info, please see http://wicketpagetest.sourceforge.net/


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Announce: wicket page test 1.1.0 available

2010-01-16 Thread Kent Tong

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 won't be including,
say, Selenium and Jetty code at runtime.

Fore more info, please see http://wicketpagetest.sourceforge.net/


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org