archiva/archiva-modules/archiva-web/archiva-webapp-test
Brett Porter f56609efad [MRM-1330] refactor access around the concept of a "repository session". See Javadoc for some notes. This should be a single entry point for application users of either the metadata repository, resolution, or storage access. The session needs to be explicitly closed (and modifications saved) to facilitate some storage mechanisms.
git-svn-id: https://svn.apache.org/repos/asf/archiva/trunk@1053542 13f79535-47bb-0310-9956-ffa450edef68
2010-12-29 06:14:04 +00:00
..
src/test merged MRM-980 branch to trunk 2010-09-28 09:09:32 +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 [MRM-1330] refactor access around the concept of a "repository session". See Javadoc for some notes. This should be a single entry point for application users of either the metadata repository, resolution, or storage access. The session needs to be explicitly closed (and modifications saved) to facilitate some storage mechanisms. 2010-12-29 06:14:04 +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