[
https://issues.apache.org/jira/browse/TAP5-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922687#action_12922687
]
Hudson commented on TAP5-1315:
------------------------------
Integrated in tapestry-5.2-freestyle #212 (See
[https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/212/])
TAP5-1315: Simplify testSetup() to get all test parameters from the XMLTest
object (rather than via method parameters)
TAP5-1315: Eliminate the need for SeleniumLauncher; allow a TestCase to set up
Selenium RC & Jetty by itself
> Allow individual SeleniumTestCases to run w/o configuring SeleniumLauncher
> --------------------------------------------------------------------------
>
> Key: TAP5-1315
> URL: https://issues.apache.org/jira/browse/TAP5-1315
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-test
> Affects Versions: 5.2.2
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.2
>
>
> This has been a big problem, the fact that you need SeleniumLauncher
> configured to run any selenium tests, which breaks the ability to run
> individual tests (they fail because Selenium & Jetty are not running).
> A fix for this has been discussed on the list, where SeleniumTestCase base
> class is responsible for starting and stopping servers (what SeleniumLauncher
> does today).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
