Date: 2009-03-18 13:46:30 +0000 (Wed, 18 Mar 2009)
added some comments
--- test/accessplatform/trunk/testrunner.j2ee/README.txt 2009-03-18 13:43:18 UTC (rev 5624)
+++ test/accessplatform/trunk/testrunner.j2ee/README.txt 2009-03-18 13:46:30 UTC (rev 5625)
@@ -67,6 +67,23 @@
invoking tests with a browser, set the line "<wait>false</wait>" to "<wait>true</wait>"
in the pom.xml. Using "cargo:deploy", you should be able to hot-deploy.
+An example URL for invoking tests via your browser:
+Connection property filenames are passed in as system properties to the appserver, see "cargo.jvmargs"
+in the pom.xml. The expected property names depend on the implementation of test.framework's TestHelper.
If you experiment with different PMF configuration files, please note that
TestHelper will do a System.exit() when it doesn't find a PMF properties file.
This will miraculously shut down the application server.
+The versions of the test suites currently are hard-coded in the web.xml. So if you get something like
+"No testsuites found", the version of the testsuite is likely to be different from what you have in web.xml.
\ No newline at end of file
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.