Questions for 2.x: Archetypes and UI Testing

6 messages Options
Embed this post
Permalink
mraible

Questions for 2.x: Archetypes and UI Testing

Reply Threaded More More options
Print post
Permalink
A couple of questions for folks using (or planning to use) 2.x:

1. As far as archetypes go, are you using basic or modular?

2. If there was a 3rd type of archetype that included the full source
(like AppFuse 1.x), would you use it over the existing basic or
modular archetypes?  If yes, I'm assuming upgrading is not that big of
an issue for you?

3. Do you use the Canoo WebTests?  If not, how do you do UI testing?
If so, would you prefer Selenium?

<rambling>
On my current project, I integrated Selenium to replace Canoo and got
tests working in both IE and Firefox (I even found a bug that only
happens in IE). The HTML-based tests are great for running in Selenium
IDE and using the <selenese> Ant task, but they don't allow i18n or
dynamic values AFAICT. I've gotten the Java-based tests working as
well.  I think it's good to support both, but it probably makes sense
to use the Java-based tests in AppFuse core if we're going to
replicate the current functionality where we can test all locales.  Of
course, we could probably parse/replace keys in the HTML files, but
that sounds XDoclet-ish where it works from Maven, but not very well
from the IDE.
</rambling>

Thanks,

Matt

--
http://raibledesigns.com

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

viggo

Re: Questions for 2.x: Archetypes and UI Testing

Reply Threaded More More options
Print post
Permalink
1. I've used modular projects so far (struts and Spring MVC). I think that using modular projects is the way to go. Normally you will have business logic that you perhaps want to expose through other channels than web or reuse, so it's better to separate it in an own module.

2. I think in some cases that I would use the full source archetype. In some contexts it could be useful to start with full sourcecode and modify it instead of tweaking the bundled logic in a way that makes you happy. An example would of course be the core model classes, which sometimes make sense to modify. And yes, upgrading would in that case not be an issue.

3. In other projects we have used JMeter, and have been happy with that. I've read some Selenium documentation, but haven't been convinsed to change so far.

mraible wrote:
A couple of questions for folks using (or planning to use) 2.x:

1. As far as archetypes go, are you using basic or modular?

2. If there was a 3rd type of archetype that included the full source
(like AppFuse 1.x), would you use it over the existing basic or
modular archetypes?  If yes, I'm assuming upgrading is not that big of
an issue for you?

3. Do you use the Canoo WebTests?  If not, how do you do UI testing?
If so, would you prefer Selenium?

<rambling>
On my current project, I integrated Selenium to replace Canoo and got
tests working in both IE and Firefox (I even found a bug that only
happens in IE). The HTML-based tests are great for running in Selenium
IDE and using the <selenese> Ant task, but they don't allow i18n or
dynamic values AFAICT. I've gotten the Java-based tests working as
well.  I think it's good to support both, but it probably makes sense
to use the Java-based tests in AppFuse core if we're going to
replicate the current functionality where we can test all locales.  Of
course, we could probably parse/replace keys in the HTML files, but
that sounds XDoclet-ish where it works from Maven, but not very well
from the IDE.
</rambling>

Thanks,

Matt

--
http://raibledesigns.com

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

Re: Questions for 2.x: Archetypes and UI Testing

Reply Threaded More More options
Print post
Permalink
In reply to this post by mraible
On Wed, 7 Mar 2007 12:01:50 -0700, Matt Raible wrote
> A couple of questions for folks using (or planning to use) 2.x:
>
> 1. As far as archetypes go, are you using basic or modular?

At this stage, basic. My app won't be much more than a webapp.

> 2. If there was a 3rd type of archetype that included the full source
> (like AppFuse 1.x), would you use it over the existing basic or
> modular archetypes?  If yes, I'm assuming upgrading is not that big
> of an issue for you?

No, but that's only because I suspect it's possible to extend Appfuse's user
model using Hibernate rather than messing with your code. (I'd like to
decouple addresses from users, since users may have 1-n addresses but so could
other things like a cart's shipping address. I don't know if that's good
design but it seems reasonable)

> 3. Do you use the Canoo WebTests?  If not, how do you do UI testing?
> If so, would you prefer Selenium?

Canoo.

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

jloken

RE: Questions for 2.x: Archetypes and UI Testing

Reply Threaded More More options
Print post
Permalink
In reply to this post by mraible
Hi,
1. We have not upgraded from version 1.9.3 yet. Still need to research
which is the best option.

2. We have made a number of changes to the AppFuse code and vote for
having a full source archetype.
It is true that upgrading AppFuse code will then be more cumbersome, but
I must live with this.
If a full source archetype is not included, then I will have to use your
development tree to get the source code, move it to our basic/modular
archetype, then merge our code into it. Having a full source archetype
will therefore save time

3. We do use Canoo WebTests, but find it has it's limitations, takes a
long time to tweak the script! Selenium looks very promising. It is good
news if it is possible, as you mentioned, to use Selenium IDE to quickly
create scripts, and then to use <selenese> Ant task.

Many thanks,
Jon
 

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Matt
Raible
Sent: 07 March 2007 19:02
To: AppFuse
Subject: [appfuse-user] Questions for 2.x: Archetypes and UI Testing

A couple of questions for folks using (or planning to use) 2.x:

1. As far as archetypes go, are you using basic or modular?

2. If there was a 3rd type of archetype that included the full source
(like AppFuse 1.x), would you use it over the existing basic or modular
archetypes?  If yes, I'm assuming upgrading is not that big of an issue
for you?

3. Do you use the Canoo WebTests?  If not, how do you do UI testing?
If so, would you prefer Selenium?

<rambling>
On my current project, I integrated Selenium to replace Canoo and got
tests working in both IE and Firefox (I even found a bug that only
happens in IE). The HTML-based tests are great for running in Selenium
IDE and using the <selenese> Ant task, but they don't allow i18n or
dynamic values AFAICT. I've gotten the Java-based tests working as well.
I think it's good to support both, but it probably makes sense to use
the Java-based tests in AppFuse core if we're going to replicate the
current functionality where we can test all locales.  Of course, we
could probably parse/replace keys in the HTML files, but that sounds
XDoclet-ish where it works from Maven, but not very well from the IDE.
</rambling>

Thanks,

Matt

--
http://raibledesigns.com

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

Struts2 Fan

RE: Questions for 2.x: Archetypes and UI Testing

Reply Threaded More More options
Print post
Permalink
For UI Testing I think Apache JMeter is cool and it is well supported. I just looked at the selenium. It seems nice too but I always prefer Apache projects.
Jakobsen, Peder

RE: RE: Questions for 2.x: Archetypes and UI Testing

Reply Threaded More More options
Print post
Permalink
Hi,

If you have not tried Selenium, make sure you play with it for a couple of days before you make up your mind.

For one, comparing Selenium to JMeter is perhaps a misunderstanding of what Selium is and what it can do.

Also, if you always prefer Apache projects, these days it seems like some of the lamest projects are Apache ones, while really cool ones are hosted elsewhere now that the rest of the world has realized that Open Source is the way to go.  Check IBM Glassfish or Grails for example, etc. etc. etc. etc..

Selenium is a truly awsome tool, couldn't imagine doing a serious web development project without it anymore.  A+

Peder :)

-----Original Message-----
From: Struts2 Fan [mailto:[hidden email]]
Sent: March 12,2007 7:44 AM
To: [hidden email]
Subject: [appfuse-user] RE: Questions for 2.x: Archetypes and UI Testing



For UI Testing I think Apache JMeter is cool and it is well supported. I just
looked at the selenium. It seems nice too but I always prefer Apache
projects.
--
View this message in context: http://www.nabble.com/Questions-for-2.x%3A-Archetypes-and-UI-Testing-tf3364157s2369.html#a9432984
Sent from the AppFuse - User mailing list archive at Nabble.com.

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


This e-mail originates from the City of Ottawa e-mail system. Any
distribution, use or copying of this e-mail or the information it
contains by other than the intended recipient(s) is unauthorized.
If you are not the intended recipient, please notify me at the
telephone number shown above or by return e-mail and delete this
communication and any copy immediately. Thank you.

Le présent courriel a été expédié par le système de courriels de
la Ville d'Ottawa. Toute distribution, utilisation ou reproduction
du courriel ou des renseignements qui s'y trouvent par une
personne autre que son destinataire prévu est interdite. Si vous
avez reçu le message par erreur, veuillez m'en aviser par
téléphone (au numéro précité) ou par courriel, puis supprimer sans
délai la version originale de la communication ainsi que toutes
ses copies. Je vous remercie de votre collaboration.

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