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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to