Optionally use existing selenium server in selenese goal
--------------------------------------------------------

                 Key: MSELENIUM-48
                 URL: http://jira.codehaus.org/browse/MSELENIUM-48
             Project: Maven 2.x Selenium Plugin
          Issue Type: New Feature
          Components: selenese
    Affects Versions: 1.0-rc-1
            Reporter: Craig
            Assignee: Jason Dillon


I have a junit integration test that uses selenium, and is run by surefire. I 
also have html-style selenium IDE test executed by the selenese goal. To run 
both kinds of tests, this is my configuration:
<build>
<plugins>
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-surefire-plugin</artifactId>
    <executions>
      <execution>
        <id>test</id>
        <phase>test</phase>
        <goals>
          <goal>test</goal>
        </goals>
        <configuration>
          <includes>
            <include>**/*SeleniumTest*</include>
          </includes>
        </configuration>
      </execution>
    </executions>
  </plugin>
<plugin>
 <groupId>org.codehaus.mojo</groupId>
 <artifactId>selenium-maven-plugin</artifactId>
 <executions>

  <execution>
   <id>start</id>
   <phase>pre-integration-test</phase>
   <goals>
    <goal>start-server</goal>
   </goals>
   <configuration>
    <background>true</background>
    <logOutput>true</logOutput>
    <multiWindow>true</multiWindow>
   </configuration>
  </execution>
 
  <execution>
   <id>stop</id>
   <phase>post-integration-test</phase>
   <goals>
    <goal>stop-server</goal>
   </goals>
  </execution>
 </executions>
</plugin>
  <plugin>
    <groupId>org.codehaus.mojo</groupId>
    <artifactId>selenium-maven-plugin</artifactId>
    <configuration>
      <browser>*firefoxproxy</browser>
      <suite>src/test/selenium/suite.html</suite>
      <startURL>http://localhost</startURL>
      <multiWindwow>true</multiWindwow>
    </configuration>
    <executions>
      <execution>
        <id>integration-test</id>
        <phase>integration-test</phase>
        <goals>
          <goal>selenese</goal>
        </goals>
      </execution>
    </executions>
  </plugin>
</plugins>
</build>

When the selenese goal is reached, it tries to start another selenium server, 
and fails because the port is already in use. Can you add a configuration 
option to the selenese goal so it can use an existing selenium server, instead 
of starting a new one? This change would also allow users to run their 
html-style tests on remote selenium servers, too.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to