Skip to content
This repository has been archived by the owner on Nov 17, 2017. It is now read-only.

Latest commit

 

History

History
executable file
·
32 lines (19 loc) · 1.96 KB

README.markdown

File metadata and controls

executable file
·
32 lines (19 loc) · 1.96 KB
Raw

Readme file for showcase-ftests

How to run tests:

The tests can be run from command line with this command, assuming that your current directory is the directory with showcase-ftests:

    $ mvn clean verify -PnameOfTheProfile [-Dtest=nameOfTheTest] [-Dshowcase.classifier=classifier] [-Darquillian.launch=whichSettingsForContainer] [-Dtomcat6Zip=path/to/your/tomcat6/zip] [-Dtomcat7Zip=path/to/your/tomcat7/zip]

  • nameOfTheProfile - for example jbossas-managed-7-1, all profiles can be found in pom.xml

  • nameOfTheTest - define the test which will be run, it is optional, when not assigned all tests are run

  • showcase.classifier - for various containers there is need to deploy various showcase wars, jee6(default)

  • whichSettingsForContainer - when this is set, the configuration for container with qualifier whichSettingsForContainer will be launched, different qualifiers can be set in arquillian.xml

  • tomcat6Zip and tomcat7Zip flags are mandatory in case you want to test on Tomcat 6 or 7 respectively, the path should point to the Tomcat distribution zip file, versions of Tomcat distributions are defined in the parent pom.xml

Notes:

  • note that binary distributions for JBoss containers are downloaded automatically as maven dependencies. You can also use your binaries, but you have to assign correct path to the containers installations in src/test/resources/arquillian.xml

  • when testing on Tomcats 6 or 7, one has to set -Dtomcat6Zip or -Dtomcat7Zip respectively, to point to zipped Tomcat distributions

  • It is recommended to use vncsession.sh script, to run tests in other desktop, since some of them are sensitive on mouse movements, clicks etc.

  • these tests require selenium-server running, which you can start manually with selenium-server.sh script, or you can let Arquillian framework do that for you, by setting the skip property to false(default) for selenium-server qualifier in src/test/resources/arquillian.xml