archiva/archiva-modules/archiva-web/archiva-webapp-test
Olivier Lamy c6066ec4b2 upgrade selenium version used
git-svn-id: https://svn.apache.org/repos/asf/archiva/trunk@1165352 13f79535-47bb-0310-9956-ffa450edef68
2011-09-05 16:35:11 +00:00
..
src/test start working on fixing issue with selenium tests 2011-09-05 16:34:57 +00:00
ReadMe.txt [MRM-1372] Outdated instruction for Maven and JUnit still in ReadMe.txt for selenium tests 2010-04-13 06:55:01 +00:00
pom.xml upgrade selenium version used 2011-09-05 16:35:11 +00:00

ReadMe.txt

ReadMe
----------
Run selenium tests in src/test/testng with Maven and TestNG
  - mvn clean install 

Run Selenium tests in src/test/testng against an existing Archiva instance
  - Start Archiva
  - Configure admin user for archiva (match values in src/test/resources/testng.properties )
  - modify src/test/resources/testng.properties as needed
  - mvn clean install -Dcontainer-existing

The Cargo installations are stored outside of target to avoid multiple downloads.
To remove the Cargo installations and re-download them next run, use:
  - mvn -Pclean-cargo clean

Internet Explorer and Safari users must disable their popup blockers. Using *iexplore as
the browser requires running as an Administrator on Windows 7/Vista, or alternatively you
can use *iexploreproxy.


  

IMPORTANT:

When writing Selenium tests for artifact upload, please avoid using the "test" syllable/word for 
the groupId or artifactId (ex. test.group:testAddArtifactValidValues:1.0) as this is used for the 
search tests. The tests explicitly assert the returned number of hits for searching an artifact with 
a groupId or artifactId containing the word "test", so if you upload or add a new artifact which has
the term "test", the number of hits will be different and the search tests will fail.

See org.apache.archiva.web.test.SearchTest.java or read the related thread discussion at
http://old.nabble.com/Selenium-tests-failure-in-trunk-td27830786.html