continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From José Morales Martínez <>
Subject RE: Reviving the automated Selenium tests
Date Mon, 16 Feb 2009 16:15:25 GMT
Thank you very much for the instructions.

I'll start with the option A. Once I was familiar with the test, try researching a little
on the line B.

In principle, I will try to generate tests using Java classes. 	
In my opinion, this option is more reusable and can manage the state of the application.


-----Mensaje original-----
De: Wendy Smoak []
Enviado el: vie 13/02/2009 22:57
Asunto: Re: Reviving the automated Selenium tests
On Thu, Feb 12, 2009 at 1:31 PM, José Morales Martínez <> wrote:

> I am interested in this topic.
> I think that this would avoid many of the problems has been the change to strut2.
> How can I contribute?  Test will be attached to Jira issues?

Great!  Yes, tests can be contributed by opening a JIRA issue and
attaching a patch.

What I'm working on right now is getting the container
start/deploy/stop part automated again.

I've got three parallel efforts going in the continuum-webapp-test module.

1. in continuum-webapp, run 'mvn jetty:run'
2., in continuum-webapp-test, run 'mvn clean install'

This will use the default pom.xml, and should work.  With the webapp
running as the root context on port 9090, you should get a successful
test of the About page.  If you want to run tests against another
Continuum instance, edit the url in src/test/resources/ .

Unfortunately, that's the *only* thing that works right now, but if
you're more interested in writing tests than messing with the
infrastructure, start there. :)

Or, if you prefer Selenium IDE, you can record tests with that and
contribute the html files.  You'll find some of those tests in
src/test/selenium-ide, and Emmanuel mentioned the idea of
automatically converting them to Java during the build and running

1. in continuum-webapp-test, run 'mvn clean install -f it-pom.xml'

This should use the Cargo plugin to start Tomcat and deploy the webapp
as /continuum on port 9595.  This needs the latest and greatest Cargo,
which you'll probably have to build yourself.  You'll see
configuration for the data sources and extra dependency jars in the
pom-it.xml file -- this is new stuff in Cargo.

This one has the most promise.  I'm pretty sure it actually worked
once, earlier today, but it's being uncooperative now and I've been
staring at it for too long to see the problem.

1. edit and change BASE_URL to
2. in continuum-webapp-test, run 'mvn clean install -f pom2.xml'

This should use the JUnit CargoTestSetup class to start Tomcat and
deploy the webapp.  It requires a TOMCAT_HOME environment variable set
to the location of a Tomcat 5.5 install.  I still need to add the
Resources and figure out how to get the extra jars into the Tomcat

This one isn't ready for general consumption yet.  Some things may
still be specific to my environment while I try to get it working.
It's a continuation of some work I did ages ago, and probably isn't
what we'll end up using.

Hope that is enough to get started with, if you have any questions, just ask.


Este mensaje, y en su caso, cualquier fichero anexo al mismo,
 puede contener informacion clasificada por su emisor como confidencial
 en el marco de su Sistema de Gestion de Seguridad de la 
Informacion siendo para uso exclusivo del destinatario, quedando 
prohibida su divulgacion copia o distribucion a terceros sin la 
autorizacion expresa del remitente. Si Vd. ha recibido este mensaje 
 erroneamente, se ruega lo notifique al remitente y proceda a su borrado. 
Gracias por su colaboracion.
This message including any attachments may contain confidential 
information, according to our Information Security Management System,
 and intended solely for a specific individual to whom they are addressed.
 Any unauthorised copy, disclosure or distribution of this message
 is strictly forbidden. If you have received this transmission in error,
 please notify the sender immediately and delete it.

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message