From line 0 changed to line 0:
Testing of Weld archetypes is almost fully automated. This consists of unit and functional tests. Functional tests are written in Java using Selenium framework. All the process of testing is made easy by leveraging Maven builds. Currently, there are three types of projects which can be generated by Weld archetypes:
Testing of Weld archetypes is almost fully automated. This consists of unit and functional tests. Functional tests are written in Java using Selenium framework. All the process of testing is made easy by leveraging Maven builds. Currently, there are three types of projects which can be generated with Weld archetypes:
From line 19 changed to line 19:
Lets refer to archetypes firectory as $ARCHETYPES.
Lets refer to the archetypes directory as $ARCHETYPES.
From line 50 changed to line 50:
This kind of testsuite can be executed with GlassfishV3 standalone or JBoss AS 6.0.0.M2 container. Before you can run the testsuite you have to download one of these containers, unpack it and set environment variable to point to the installation (JBOSS\_HOME for JBossAS and GLASSFISH\_HOME for GlassfishV3). You can download JBossAS [here=>http://www.jboss.org/jbossas/downloads/] and GlassfishV3 [here=>http://download.java.net/glassfish/v3/release/]. The following commands will run the testsuite.
This kind of testsuite can be executed with GlassfishV3 standalone or JBoss AS 6.0.0.M2 container. Before you can run the testsuite you have to download one of these containers, unpack it and set environment variable to point to the installation (JBOSS\_HOME for JBossAS and GLASSFISH\_HOME for GlassfishV3). You can download JBossAS [here=>http://www.jboss.org/jbossas/downloads/] and GlassfishV3 [here=>http://download.java.net/glassfish/v3/release/]. JBossAS has to be started manually, Glassfish will start automatically from within maven build. The following commands will run the testsuite.
From line 65 changed to line 65:
Running this kind of testsuite is basically the same as the previouos one. Only difference is the directory where you run the mvn command.
Running this kind of testsuite is basically the same as the previous one. Only difference is the directory where you run the mvn command.
From line 75 changed to line 75:
All the properties passed to Selenium are defined as Maven properties, you can override them by flags in Maven command line. Main promerties can be found at pom.xml file under $ARCHETYPES directory.
All the properties passed to Selenium are defined as Maven properties, you can override them by flags in Maven command line. Main properties can be found at pom.xml file under $ARCHETYPES directory.