cancel
Showing results for 
Search instead for 
Did you mean: 

How do I need to do to run nuxeo's Selenium/Webdriver tests?

jadtn_
Champ on-the-rise
Champ on-the-rise

Hi, I've been trying to run nuxeo's Selenium and WebDriver tests for the past few days and have not gotten anywhere. Here's what I have done:

$ git clone git://github.com/nuxeo/nuxeo.git
$ cd nuxeo
$ python clone.py release-5.5

then I added the nuxeo repositories to a few pom.xml files that were complaining, then I did:

$ mvn clean install

that took a while to complete. Then I set the database's environment variables, and then:

$ cd nuxeo/nuxeo-distribution/nuxeo-distribution-tomcat-tests
$ mvn integration-test -Pmysql

but then maven hangs at running ITTests, and nothing happens for a long time. I've looked at a number of various places for running Selenium tests for nuxeo, and I tried all the commands they had listed to no avail.

Please help!

1 ACCEPTED ANSWER

Julien_Carsique
Elite Collaborator
Elite Collaborator

Hi,

then I added the nuxeo repositories to a few pom.xml files that were complaining

You should not have to do that. Could you provide some details about those errors?
/> Also, you don't need to build the whole Nuxeo source tree in order run only some modules: the missing artifacts are downloaded by Maven.

Anyway, you ended at the right place: nuxeo-distribution-tomcat-tests is running a few WebDriver tests. Another interesting module is nuxeo-distribution-dm/ftest/selenium which is running the main Selenium suites.
/> Give a look at its README, usually mvn verify is enough for running the tests. Later, you can customize the tests using various properties and profiles.

You must know there are some issues between Selenium/WebDriver and Firefox/Chrome depending on their respective versions. In 5.5, some tests were working better with Firefox 3.6 whereas others (the newest WebDriver tests) required Firefox > 5. Since 5.5, we started migrating all tests to WebDriver, using the latest driver working with newer Firefox versions.

The migration from Selenium to WebDriver is still a work in progress but we already did some refactoring and cleanup in the involved modules. We also slightly improved the documentation and README files. Maybe you should first try with the 5.6-SNAPSHOT branch and look at the modules' listing. I would recommend to start with the Selenium and WebDriver tests for DM.

View answer in original post

4 REPLIES 4

Julien_Carsique
Elite Collaborator
Elite Collaborator

Hi,

then I added the nuxeo repositories to a few pom.xml files that were complaining

You should not have to do that. Could you provide some details about those errors?
/> Also, you don't need to build the whole Nuxeo source tree in order run only some modules: the missing artifacts are downloaded by Maven.

Anyway, you ended at the right place: nuxeo-distribution-tomcat-tests is running a few WebDriver tests. Another interesting module is nuxeo-distribution-dm/ftest/selenium which is running the main Selenium suites.
/> Give a look at its README, usually mvn verify is enough for running the tests. Later, you can customize the tests using various properties and profiles.

You must know there are some issues between Selenium/WebDriver and Firefox/Chrome depending on their respective versions. In 5.5, some tests were working better with Firefox 3.6 whereas others (the newest WebDriver tests) required Firefox > 5. Since 5.5, we started migrating all tests to WebDriver, using the latest driver working with newer Firefox versions.

The migration from Selenium to WebDriver is still a work in progress but we already did some refactoring and cleanup in the involved modules. We also slightly improved the documentation and README files. Maybe you should first try with the 5.6-SNAPSHOT branch and look at the modules' listing. I would recommend to start with the Selenium and WebDriver tests for DM.

Thanks for the pointers Julien! I finally got it working. I checked out nuxeo-distribution, and then

When not activating the customdb profile (i.e. -Pcustomdb,pgsql), then the default H2 database is used. FYI, that's managed by [the integration nuxeo-distribution-tools (Ant-like) script][1] and [the DatabaseHelper class][2]; see the README file for a list of configurable properties.

Yeah, I may have been using mvn3 when I saw the errors, but have switched to mvn2 since.

Getting started

Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.