2011-02-03 14 views
5

uso carico di maven e selenio per l'automazione. ecco il codice:maven cargo e selenio

<plugin> 
      <groupId>org.codehaus.cargo</groupId> 
      <artifactId>cargo-maven2-plugin</artifactId> 
      <version>1.0.5</version> 
      <configuration> 
       <wait>false</wait> 
       <container> 
        <containerId>tomcat6x</containerId> 
        <zipUrlInstaller> 
         <url> 
          http://mirrors.enquira.co.uk/apache/tomcat/tomcat-6/v6.0.30/bin/apache-tomcat-6.0.30.zip 
         </url> 
         <installDir>${installDir}</installDir> 
        </zipUrlInstaller> 
        <output> 
         ${project.build.directory}/tomcat6x.log 
        </output> 
        <log>${project.build.directory}/cargo.log</log> 
       </container> 
       <configuration> 
        <home> 
         ${project.build.directory}/tomcat6x/container 
        </home> 
        <properties> 
         <cargo.logging>high</cargo.logging> 
         <cargo.servlet.port>8081</cargo.servlet.port> 
        </properties> 
        <files> 
         <copy> 
          <file>${project.basedir}/src/main/resources/datasource.properties</file> 
          <todir>webapps</todir> 
          <configfile>true</configfile> 
          <overwrite>true</overwrite> 
         </copy> 
        </files> 
        <properties> 
         <customMessage>${catalina.home}</customMessage> 
        </properties> 
       </configuration> 
      </configuration> 
      <executions> 
       <execution> 
        <id>start-container</id> 
        <phase>pre-integration-test</phase> 
        <goals> 
         <goal>configure</goal> 
         <goal>start</goal> 
         <goal>deploy</goal> 
        </goals> 
        <configuration> 
         <deployer> 
          <deployables> 
           <deployable> 
            <groupId>${project.groupId}</groupId> 
            <artifactId>${project.artifactId}</artifactId> 
            <type>war</type> 
            <pingURL>**the url**</pingURL> 
            <pingTimeout>180000</pingTimeout> 
            <properties> 
             <context>**war-name**</context> 
            </properties> 
           </deployable> 
          </deployables> 
         </deployer> 
        </configuration> 
       </execution> 

       <execution> 
        <id>stop-container</id> 
        <phase>post-integration-test</phase> 
        <goals> 
         <goal>stop</goal> 
        </goals> 
       </execution> 
      </executions> 

ma come la guerra ha iniziato sempre più grande il PingTimeout ha iniziato ad aumentare, io non voglio usare ping timeout, ma sono costretti a in questo momento, come l'implementazione richiede un po 'di tempo e il selenio non aspetta se il pingtimeout non è menzionato.

c'è qualche soluzione a questo problema?

+0

Could http://stackoverflow.com/questions/1498967/help-with-selenium-maven-cargo essere parenti? – Raghuram

risposta

1

Che dire dell'utilizzo di Jetty? Il plugin maven-jetty attenderà fino a quando non verrà caricata la tua webapp. In alternativa, puoi utilizzare il plug-in tomcat-maven e il relativo obiettivo di distribuzione per distribuire la tua webapp su un'istanza di Tomcat in esecuzione tramite Tomcat Manager. Questo plugin attenderà anche l'esecuzione (e quindi il lancio dei test del selenio) fino a quando la guerra non verrà dispiegata.

Questa è la mia configurazione. Si avvierà Jetty, distribuire l'applicazione, lanciare Selenio, lanciare test Selenium e, infine, chiude tutti i server:

<plugin> 
     <groupId>org.mortbay.jetty</groupId> 
     <artifactId>maven-jetty-plugin</artifactId> 
     <configuration> 
      <contextPath>/</contextPath> 
      <scanIntervalSeconds>0</scanIntervalSeconds> 
     </configuration> 
     <executions> 
      <execution> 
      <id>start</id> 
      <phase>pre-integration-test</phase> 
      <goals> 
       <goal>run</goal> 
      </goals> 
      <configuration> 
       <daemon>true</daemon> 
      </configuration> 
      </execution> 
      <execution> 
      <id>stop</id> 
      <phase>post-integration-test</phase> 
      <goals> 
       <goal>stop</goal> 
      </goals> 
      </execution> 
     </executions> 
     </plugin> 

     <plugin> 
     <groupId>org.codehaus.mojo</groupId> 
     <artifactId>selenium-maven-plugin</artifactId> 
     <configuration> 
      <background>true</background> 
     </configuration> 
     <executions> 
      <execution> 
      <id>start-selenium</id> 
      <phase>pre-integration-test</phase> 
      <goals> 
       <goal>start-server</goal> 
      </goals> 
      </execution> 
      <execution> 
      <id>stop-selenium</id> 
      <phase>post-integration-test</phase> 
      <goals> 
       <goal>stop-server</goal> 
      </goals> 
      </execution> 
     </executions> 
     </plugin> 

     <plugin> 
     <groupId>org.apache.maven.plugins</groupId> 
     <artifactId>maven-surefire-plugin</artifactId> 
     <executions> 
      <execution> 
      <id>selenium-tests</id> 
      <phase>integration-test</phase> 
      <goals> 
       <goal>test</goal> 
      </goals> 
      <configuration> 
       <skip>false</skip> 
       <excludes> 
       <exclude>none</exclude> 
       </excludes> 
       <includes> 
       <include>**/*SeleniumTest.java</include> 
       </includes> 
      </configuration> 
      </execution> 
     </executions> 
     </plugin>