You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@shale.apache.org by ws...@apache.org on 2006/08/01 05:10:28 UTC

svn commit: r427419 - in /shale/framework/trunk/shale-apps: pom.xml src/site/apt/selenium.apt

Author: wsmoak
Date: Mon Jul 31 20:10:28 2006
New Revision: 427419

URL: http://svn.apache.org/viewvc?rev=427419&view=rev
Log:
Move the dependency-maven-plugin execution to the generate-sources phase so that it runs before antrun.
This should not be necessary, but Maven is executing them in the wrong order which causes a failure.
The selenium profile can now be activated with -Pselenium, or with -Dselenium as a system property.
Minor documentation improvements.
SHALE-243

Modified:
    shale/framework/trunk/shale-apps/pom.xml
    shale/framework/trunk/shale-apps/src/site/apt/selenium.apt

Modified: shale/framework/trunk/shale-apps/pom.xml
URL: http://svn.apache.org/viewvc/shale/framework/trunk/shale-apps/pom.xml?rev=427419&r1=427418&r2=427419&view=diff
==============================================================================
--- shale/framework/trunk/shale-apps/pom.xml (original)
+++ shale/framework/trunk/shale-apps/pom.xml Mon Jul 31 20:10:28 2006
@@ -67,6 +67,11 @@
         <!-- See http://shale.apache.org/shale-apps/selenium.html -->
         <profile>
             <id>selenium</id>
+            <activation>
+                <property>
+                    <name>selenium</name>
+                </property>
+            </activation>
             <build>
                 <plugins>
                     <plugin>
@@ -75,7 +80,7 @@
                         <executions>
                             <execution>
                                 <id>unzip-selenium</id>
-                                <phase>process-resources</phase>
+                                <phase>generate-resources</phase>
                                 <goals>
                                     <goal>unpack</goal>
                                 </goals>

Modified: shale/framework/trunk/shale-apps/src/site/apt/selenium.apt
URL: http://svn.apache.org/viewvc/shale/framework/trunk/shale-apps/src/site/apt/selenium.apt?rev=427419&r1=427418&r2=427419&view=diff
==============================================================================
--- shale/framework/trunk/shale-apps/src/site/apt/selenium.apt (original)
+++ shale/framework/trunk/shale-apps/src/site/apt/selenium.apt Mon Jul 31 20:10:28 2006
@@ -10,19 +10,21 @@
  Explorer. The Selenium JavaScript code is deployed alongside your running
  application, and interacts with it just as your users do.
 
- Shale uses Selenium to for functional testing of the example apps.  
+ Shale uses Selenium for functional testing of the example apps.
  The following example apps include Selenium tests:
 
   * Shale Mailreader
 
 * Install
 
- <<Download>> Selenium 0.7.0 from OpenQA, and install selenium-core-0.7.0.zip
- in your local Maven repository.
- 
+ <<Download>> Selenium 0.7.0 from OpenQA: 
  {{{http://www.openqa.org/selenium-core/download.action}
  http://www.openqa.org/selenium-core/download.action}}
 
+  []
+
+  <<Install>> selenium-core-0.7.0.zip in your local Maven repository.
+ 
 +-----+
 mvn install:install-file -DgroupId=org.openqa -DartifactId=selenium-core     \
                          -Dversion=0.7.0 -Dpackaging=zip -DgeneratePom=true  \
@@ -48,7 +50,7 @@
   webapp
 
   * copy any files in 'src/test/selenium' into the webapp
-  
+
   []
 
 +-----+
@@ -76,11 +78,24 @@
 
  <<Run>> the tests with the Selenium TestRunner.
 
- * Visit http://localhost:8080/<appname>/selenium/core/TestRunner.html
+ * Visit <<<http://localhost:8080/<appname>/selenium/core/TestRunner.html>>>
 
  * Click 'go' in the top left frame to load the TestSuite.html page
 
  * Click 'All' in the top right frame to run the tests
+
+ []
+
+ <<Run>> the tests <automatically>.
+
+ * Append <<<?test=../tests/TestSuite.html&auto=true>>>
+ to the TestRunner.html URL
+
+ []
+
+ After it runs the tests automatically, Selenium will <<<POST>>> the results to
+ the default URL of <<<../postResults>>>. Since nothing is there to process the
+ request, you will see a 404 Not Found error page in the bottom frame.
 
 
 * Edit