Moving from Canoo WebTest to Selenium

5 messages Options
Embed this post
Permalink
mraible

Moving from Canoo WebTest to Selenium

Reply Threaded More More options
Print post
Permalink
All,

After getting Dojo's DropdownDatePicker working with both Struts and
Spring MVC, I've run into a snag:

You can no longer use Canoo WebTest to enter dates in a form.

It doesn't find the form element because HtmlUnit (the underlying
browser implementation for Canoo) doesn't understand/render Dojo's
components.

For users, workarounds include:

1. Don't write tests for entering data on forms that have required dates.
2. Don't make dates required.

Either way, it seems logical to move to Selenium for UI testing.

Thoughts?

I plan to use Selenium's Java support to write the tests, so test data
will be part of JUnit reports, which is a nice side effect. Also, if
you start Cargo + Selenium RC up in the background, you'll be able to
run tests from your IDE.

Is there anyone out there that'd like the option of WebTest or
Selenium?  It's probably possible to support both, but I'd rather not.
Selenium is simply a better solution for the problem AFAICT.

Thanks in advance for any comments.

Matt

--
http://raibledesigns.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Sanjiv Jivan

Re: Moving from Canoo WebTest to Selenium

Reply Threaded More More options
Print post
Permalink
I favor only supporting Selenium. I see no reason to support a testing framework like Canoo which is no longer a web testing best practice.

Sanjiv

On 5/31/07, Matt Raible <[hidden email]> wrote:
All,

After getting Dojo's DropdownDatePicker working with both Struts and
Spring MVC, I've run into a snag:

You can no longer use Canoo WebTest to enter dates in a form.

It doesn't find the form element because HtmlUnit (the underlying
browser implementation for Canoo) doesn't understand/render Dojo's
components.

For users, workarounds include:

1. Don't write tests for entering data on forms that have required dates.
2. Don't make dates required.

Either way, it seems logical to move to Selenium for UI testing.

Thoughts?

I plan to use Selenium's Java support to write the tests, so test data
will be part of JUnit reports, which is a nice side effect. Also, if
you start Cargo + Selenium RC up in the background, you'll be able to
run tests from your IDE.

Is there anyone out there that'd like the option of WebTest or
Selenium?  It's probably possible to support both, but I'd rather not.
Selenium is simply a better solution for the problem AFAICT.

Thanks in advance for any comments.

Matt

--
http://raibledesigns.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


mraible

Re: [appfuse-user] Re: [appfuse-dev] Moving from Canoo WebTest to Selenium

Reply Threaded More More options
Print post
Permalink
I guess the hard part if figuring out how to do it. With Canoo
WebTest, it was easy enough to use svn:externals to pull in the
web-tests.xml (as well as login.xml and config.xml) from the
src/test/resources directory of each web module.

If we want to allow the same setup for Selenium, we'd likely put the
files in src/test/java/org/appfuse/webapp/selenium (or something
similar).  We could use svn:externals to pull these into the
archetypes, but we'd have to retain the package names. For the basic
archetypes, Maven will rename the package names, but not for the
modular archetypes, so it seems to make better sense to hard-code
these.

Of course, if Maven can run tests in a JAR file, that might be a good
solution (but it doesn't do much for IDE integration).

On a related note, does anyone have any thoughts about an
appfuse-junit dependency that includes all the Base*TestCase classes
and dependencies? We'll probably eventually need to do this if we want
to support TestNG and allow users to use JUnit. Then again, it's
probably best to switch whole-heartedly and not support multiple
testing frameworks.

Matt

On 5/31/07, Sanjiv Jivan <[hidden email]> wrote:

> I favor only supporting Selenium. I see no reason to support a testing
> framework like Canoo which is no longer a web testing best practice.
>
> Sanjiv
>
>
> On 5/31/07, Matt Raible <[hidden email]> wrote:
> >
> > All,
> >
> > After getting Dojo's DropdownDatePicker working with both Struts and
> > Spring MVC, I've run into a snag:
> >
> > You can no longer use Canoo WebTest to enter dates in a form.
> >
> > It doesn't find the form element because HtmlUnit (the underlying
> > browser implementation for Canoo) doesn't understand/render Dojo's
> > components.
> >
> > For users, workarounds include:
> >
> > 1. Don't write tests for entering data on forms that have required dates.
> > 2. Don't make dates required.
> >
> > Either way, it seems logical to move to Selenium for UI testing.
> >
> > Thoughts?
> >
> > I plan to use Selenium's Java support to write the tests, so test data
> > will be part of JUnit reports, which is a nice side effect. Also, if
> > you start Cargo + Selenium RC up in the background, you'll be able to
> > run tests from your IDE.
> >
> > Is there anyone out there that'd like the option of WebTest or
> > Selenium?  It's probably possible to support both, but I'd rather not.
> > Selenium is simply a better solution for the problem AFAICT.
> >
> > Thanks in advance for any comments.
> >
> > Matt
> >
> > --
> > http://raibledesigns.com
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
>


--
http://raibledesigns.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

melinate

Re: Moving from Canoo WebTest to Selenium

Reply Threaded More More options
Print post
Permalink
In reply to this post by mraible
+1 Selenium

Canoo is effective, but it has always been a pain for me.  If Selenium can deliver on the promise of simplified web ui testing I am all for it!

Nathan

----- Original Message -----
From: "Matt Raible" <[hidden email]>
To: "AppFuse Developers" <[hidden email]>, "AppFuse" <[hidden email]>
Sent: Wednesday, May 30, 2007 9:31:05 PM (GMT-0800) America/Los_Angeles
Subject: [appfuse-dev] Moving from Canoo WebTest to Selenium

All,

After getting Dojo's DropdownDatePicker working with both Struts and
Spring MVC, I've run into a snag:

You can no longer use Canoo WebTest to enter dates in a form.

It doesn't find the form element because HtmlUnit (the underlying
browser implementation for Canoo) doesn't understand/render Dojo's
components.

For users, workarounds include:

1. Don't write tests for entering data on forms that have required dates.
2. Don't make dates required.

Either way, it seems logical to move to Selenium for UI testing.

Thoughts?

I plan to use Selenium's Java support to write the tests, so test data
will be part of JUnit reports, which is a nice side effect. Also, if
you start Cargo + Selenium RC up in the background, you'll be able to
run tests from your IDE.

Is there anyone out there that'd like the option of WebTest or
Selenium?  It's probably possible to support both, but I'd rather not.
Selenium is simply a better solution for the problem AFAICT.

Thanks in advance for any comments.

Matt

--
http://raibledesigns.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

sarat.pediredla

Re: [appfuse-user] Re: [appfuse-dev] Moving from Canoo WebTest to Selenium

Reply Threaded More More options
Print post
Permalink
In reply to this post by mraible
I vote for supporting one framework completely.

Although I like the ethos of appfuse being a great mix of various frameworks, testing needs to have a first class citizen when it comes to it.

I have not had much access to TestNG, having worked with JUnit for a long time but if this is the path, then everything should be thrown behind this.

Oh, and also +1 Selenium :)

mraible wrote:
I guess the hard part if figuring out how to do it. With Canoo
WebTest, it was easy enough to use svn:externals to pull in the
web-tests.xml (as well as login.xml and config.xml) from the
src/test/resources directory of each web module.

If we want to allow the same setup for Selenium, we'd likely put the
files in src/test/java/org/appfuse/webapp/selenium (or something
similar).  We could use svn:externals to pull these into the
archetypes, but we'd have to retain the package names. For the basic
archetypes, Maven will rename the package names, but not for the
modular archetypes, so it seems to make better sense to hard-code
these.

Of course, if Maven can run tests in a JAR file, that might be a good
solution (but it doesn't do much for IDE integration).

On a related note, does anyone have any thoughts about an
appfuse-junit dependency that includes all the Base*TestCase classes
and dependencies? We'll probably eventually need to do this if we want
to support TestNG and allow users to use JUnit. Then again, it's
probably best to switch whole-heartedly and not support multiple
testing frameworks.

Matt

On 5/31/07, Sanjiv Jivan <sanjiv.jivan@gmail.com> wrote:
> I favor only supporting Selenium. I see no reason to support a testing
> framework like Canoo which is no longer a web testing best practice.
>
> Sanjiv
>
>
> On 5/31/07, Matt Raible <matt@raibledesigns.com> wrote:
> >
> > All,
> >
> > After getting Dojo's DropdownDatePicker working with both Struts and
> > Spring MVC, I've run into a snag:
> >
> > You can no longer use Canoo WebTest to enter dates in a form.
> >
> > It doesn't find the form element because HtmlUnit (the underlying
> > browser implementation for Canoo) doesn't understand/render Dojo's
> > components.
> >
> > For users, workarounds include:
> >
> > 1. Don't write tests for entering data on forms that have required dates.
> > 2. Don't make dates required.
> >
> > Either way, it seems logical to move to Selenium for UI testing.
> >
> > Thoughts?
> >
> > I plan to use Selenium's Java support to write the tests, so test data
> > will be part of JUnit reports, which is a nice side effect. Also, if
> > you start Cargo + Selenium RC up in the background, you'll be able to
> > run tests from your IDE.
> >
> > Is there anyone out there that'd like the option of WebTest or
> > Selenium?  It's probably possible to support both, but I'd rather not.
> > Selenium is simply a better solution for the problem AFAICT.
> >
> > Thanks in advance for any comments.
> >
> > Matt
> >
> > --
> > http://raibledesigns.com
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> dev-unsubscribe@appfuse.dev.java.net
> > For additional commands, e-mail: dev-help@appfuse.dev.java.net
> >
> >
>
>


--
http://raibledesigns.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@appfuse.dev.java.net
For additional commands, e-mail: dev-help@appfuse.dev.java.net