You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Marzia Forli <ma...@yahoo.com> on 2010/01/22 20:20:46 UTC

functional testing

Hi to all wicketers,

My current assignment is a pretty big web application to build with wicket. Right now I am studying the framework and in my background thread thinking about the possible problems...
One of my biggest concerns is a testing, better said functional testing. As many of you are very experienced with wicket and possibly with big web apps, could you give some advices in this area ?
Using WicketTester will be sufficient or we will have to something like selenium/webdriver ?
why using WicketTester in the first place ?
How to organize a tests ?
What is your opinion about http://code.google.com/p/enhancedwickettester/ ?
Some pitfalls and or tricks ?
Thank you...


      


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


Re: Worldwide address form

Posted by Sam Barrow <sa...@sambarrow.com>.
anybody want to work on this? i have my collection of wicket components
and this is just the type of stuff id like to be included.

On Wed, 2010-02-03 at 11:26 +0100, Per Lundholm wrote:
> If you do that, you will be a hero. ;-)
> 
> But why not, a component that handles all kinds of addresses in the world is
> a typical joint effort.
> 
>  If it is in the drop-down of countries, then it is supported. If not your
> country is supported, then contribute!
> 
> /Per
> 
> On Thu, Jan 28, 2010 at 11:30 PM, Chris Colman <chrisc@stepaheadsoftware.com
> > wrote:
> 
> > I'm just wondering if anyone knows of a sample 'world address' entry
> > form built using wicket.
> >
> > Ideally the data entry fields for the top level attributes:
> >
> > - world region
> > - country
> > - state/zone
> >
> > Would be drop down list boxes. The contents of any drop down (except the
> > world region) would be dictated by the option(s) chosen in the drop down
> > lists above it. Eg., if you change the country from Australia to USA
> > then the state/zone drop down is populated with the US states.
> >
> > I was thinking of creating an interface for the data so that a generic
> > world wide address form could be written to the interface but the
> > implementation of the interface could be tailored to the way an
> > individual app stores it's world data.
> >
> >
> > > -----Original Message-----
> > > From: Per Lundholm [mailto:per.lundholm@gmail.com]
> > > Sent: Friday, 29 January 2010 8:26 AM
> > > To: users@wicket.apache.org
> > > Subject: Re: functional testing
> > >
> > > We write tests first and use Wicket's built-in testing.
> > >
> > > It has some quirks so you may have to spend time with figuring out how
> > to
> > > click an AjaxCheckBox, for instance.
> > >
> > > The tests target the logic of the view, such as "when clicking here,
> > that
> > > other thing should be disabled".
> > >
> > > Good test coverage really pays off when you have 20 different webapps
> > and
> > > need to work some here and some there.
> > >
> > > /Per
> > >
> > > On Mon, Jan 25, 2010 at 3:52 AM, Kent Tong <ke...@cpttm.org.mo> wrote:
> > >
> > > >
> > > > For functional testing, I'd suggest Selenium.
> > > >
> > > > For unit testing of Wicket pages, I'd suggest "Wicket Page Test"
> > > > (http://wicketpagetest.sourceforge.net).
> > > >
> > > > -----
> > > > --
> > > > Kent Tong
> > > > Better way to unit test Wicket pages (
> > > > http://wicketpagetest.sourceforge.net)
> > > > Books on CXF, Axis2, Wicket, JSF (http://http://agileskills2.org)
> > > > --
> > > > View this message in context:
> > > > http://old.nabble.com/functional-testing-tp27278781p27301553.html
> > > > Sent from the Wicket - User mailing list archive at Nabble.com.
> > > >
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >



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


Re: Worldwide address form

Posted by Per Lundholm <pe...@gmail.com>.
If you do that, you will be a hero. ;-)

But why not, a component that handles all kinds of addresses in the world is
a typical joint effort.

 If it is in the drop-down of countries, then it is supported. If not your
country is supported, then contribute!

/Per

On Thu, Jan 28, 2010 at 11:30 PM, Chris Colman <chrisc@stepaheadsoftware.com
> wrote:

> I'm just wondering if anyone knows of a sample 'world address' entry
> form built using wicket.
>
> Ideally the data entry fields for the top level attributes:
>
> - world region
> - country
> - state/zone
>
> Would be drop down list boxes. The contents of any drop down (except the
> world region) would be dictated by the option(s) chosen in the drop down
> lists above it. Eg., if you change the country from Australia to USA
> then the state/zone drop down is populated with the US states.
>
> I was thinking of creating an interface for the data so that a generic
> world wide address form could be written to the interface but the
> implementation of the interface could be tailored to the way an
> individual app stores it's world data.
>
>
> > -----Original Message-----
> > From: Per Lundholm [mailto:per.lundholm@gmail.com]
> > Sent: Friday, 29 January 2010 8:26 AM
> > To: users@wicket.apache.org
> > Subject: Re: functional testing
> >
> > We write tests first and use Wicket's built-in testing.
> >
> > It has some quirks so you may have to spend time with figuring out how
> to
> > click an AjaxCheckBox, for instance.
> >
> > The tests target the logic of the view, such as "when clicking here,
> that
> > other thing should be disabled".
> >
> > Good test coverage really pays off when you have 20 different webapps
> and
> > need to work some here and some there.
> >
> > /Per
> >
> > On Mon, Jan 25, 2010 at 3:52 AM, Kent Tong <ke...@cpttm.org.mo> wrote:
> >
> > >
> > > For functional testing, I'd suggest Selenium.
> > >
> > > For unit testing of Wicket pages, I'd suggest "Wicket Page Test"
> > > (http://wicketpagetest.sourceforge.net).
> > >
> > > -----
> > > --
> > > Kent Tong
> > > Better way to unit test Wicket pages (
> > > http://wicketpagetest.sourceforge.net)
> > > Books on CXF, Axis2, Wicket, JSF (http://http://agileskills2.org)
> > > --
> > > View this message in context:
> > > http://old.nabble.com/functional-testing-tp27278781p27301553.html
> > > Sent from the Wicket - User mailing list archive at Nabble.com.
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

Worldwide address form

Posted by Chris Colman <ch...@stepaheadsoftware.com>.
I'm just wondering if anyone knows of a sample 'world address' entry
form built using wicket.

Ideally the data entry fields for the top level attributes:

- world region
- country
- state/zone 

Would be drop down list boxes. The contents of any drop down (except the
world region) would be dictated by the option(s) chosen in the drop down
lists above it. Eg., if you change the country from Australia to USA
then the state/zone drop down is populated with the US states.

I was thinking of creating an interface for the data so that a generic
world wide address form could be written to the interface but the
implementation of the interface could be tailored to the way an
individual app stores it's world data.


> -----Original Message-----
> From: Per Lundholm [mailto:per.lundholm@gmail.com]
> Sent: Friday, 29 January 2010 8:26 AM
> To: users@wicket.apache.org
> Subject: Re: functional testing
> 
> We write tests first and use Wicket's built-in testing.
> 
> It has some quirks so you may have to spend time with figuring out how
to
> click an AjaxCheckBox, for instance.
> 
> The tests target the logic of the view, such as "when clicking here,
that
> other thing should be disabled".
> 
> Good test coverage really pays off when you have 20 different webapps
and
> need to work some here and some there.
> 
> /Per
> 
> On Mon, Jan 25, 2010 at 3:52 AM, Kent Tong <ke...@cpttm.org.mo> wrote:
> 
> >
> > For functional testing, I'd suggest Selenium.
> >
> > For unit testing of Wicket pages, I'd suggest "Wicket Page Test"
> > (http://wicketpagetest.sourceforge.net).
> >
> > -----
> > --
> > Kent Tong
> > Better way to unit test Wicket pages (
> > http://wicketpagetest.sourceforge.net)
> > Books on CXF, Axis2, Wicket, JSF (http://http://agileskills2.org)
> > --
> > View this message in context:
> > http://old.nabble.com/functional-testing-tp27278781p27301553.html
> > Sent from the Wicket - User mailing list archive at Nabble.com.
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >

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


Re: functional testing

Posted by Per Lundholm <pe...@gmail.com>.
We write tests first and use Wicket's built-in testing.

It has some quirks so you may have to spend time with figuring out how to
click an AjaxCheckBox, for instance.

The tests target the logic of the view, such as "when clicking here, that
other thing should be disabled".

Good test coverage really pays off when you have 20 different webapps and
need to work some here and some there.

/Per

On Mon, Jan 25, 2010 at 3:52 AM, Kent Tong <ke...@cpttm.org.mo> wrote:

>
> For functional testing, I'd suggest Selenium.
>
> For unit testing of Wicket pages, I'd suggest "Wicket Page Test"
> (http://wicketpagetest.sourceforge.net).
>
> -----
> --
> Kent Tong
> Better way to unit test Wicket pages (
> http://wicketpagetest.sourceforge.net)
> Books on CXF, Axis2, Wicket, JSF (http://http://agileskills2.org)
> --
> View this message in context:
> http://old.nabble.com/functional-testing-tp27278781p27301553.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

Re: functional testing

Posted by Kent Tong <ke...@cpttm.org.mo>.
For functional testing, I'd suggest Selenium.

For unit testing of Wicket pages, I'd suggest "Wicket Page Test"
(http://wicketpagetest.sourceforge.net).

-----
--
Kent Tong
Better way to unit test Wicket pages (http://wicketpagetest.sourceforge.net)
Books on CXF, Axis2, Wicket, JSF (http://http://agileskills2.org)
-- 
View this message in context: http://old.nabble.com/functional-testing-tp27278781p27301553.html
Sent from the Wicket - User mailing list archive at Nabble.com.


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


Re: functional testing

Posted by "nmelendez@getsense.com.ar" <nm...@getsense.com.ar>.
Consider using Junit for business layer and Selenium for view layer.
I use that,but my project is small.
And don't use watir, i had a bad experience with it.
NM

On Fri, Jan 22, 2010 at 4:20 PM, Marzia Forli <ma...@yahoo.com>wrote:

> Hi to all wicketers,
>
> My current assignment is a pretty big web application to build with wicket.
> Right now I am studying the framework and in my background thread thinking
> about the possible problems...
> One of my biggest concerns is a testing, better said functional testing. As
> many of you are very experienced with wicket and possibly with big web apps,
> could you give some advices in this area ?
> Using WicketTester will be sufficient or we will have to something like
> selenium/webdriver ?
> why using WicketTester in the first place ?
> How to organize a tests ?
> What is your opinion about http://code.google.com/p/enhancedwickettester/?
> Some pitfalls and or tricks ?
> Thank you...
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>