Following protocol to have my suggestions discussed here.
Suggestion:
Include a class in tapestry-test that only launches Selenium, not Jetty at
all. This lets you run tests where you've launched the application in some
other way (various maven plugins, etc. )
Provided implementation:
public class SeleniumOnly extends SeleniumLauncher
{
@Override
protected Runnable launchWebServer(
String webAppFolder, String contextPath, int port, int sslPort
) throws Exception
{
System.out.println(" webserver start");
return new Runnable()
{
@Override
public void run()
{
System.out.println(" webserver stop");
}
};
}
}
Sample testng.xml:
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd";>
<suite name="Schema Tool Test Test" annotations="1.5" verbose="2">
<parameter name="tapestry.base-url"
value="http://localhost:8083/EdenSchemaTool/"/>
<parameter name="tapestry.port" value="8083"/>
<parameter name="tapestry.context-path" value="/EdenSchemaTool"/>
<test name="EdenSchemaTool">
<packages>
<package name="com.paceap.eden.schematool.test" />
</packages>
<classes>
<class name="com.paceap.eden.schematool.test.SeleniumOnly"/>
</classes>
</test>
</suite>
Sample pom.xml excerpt:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<skip>true</skip>
<suiteXmlFiles>
<suiteXmlFile>src/test/conf/testng.xml</suiteXmlFile>
</suiteXmlFiles>
</configuration>
<executions>
<execution>
<id>integration-tests</id>
<phase>integration-test</phase>
<goals>
<goal>test</goal>
</goals>
<configuration>
<skip>false</skip>
<suiteXmlFiles>
<suiteXmlFile>src/test/conf/testng.xml</suiteXmlFile>
</suiteXmlFiles>
</configuration>
</execution>
</executions>
</plugin>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
