You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/10/19 02:22:27 UTC
[jira] Created: (TAP5-1315) Allow individual SeleniumTestCases to
run w/o configuring SeleniumLauncher
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
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.
[jira] Closed: (TAP5-1315) Allow individual SeleniumTestCases to
run w/o configuring SeleniumLauncher
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1315.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.2.2
> 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.
[jira] Commented: (TAP5-1315) Allow individual SeleniumTestCases to
run w/o configuring SeleniumLauncher
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (TAP5-1315) Allow individual SeleniumTestCases to
run w/o configuring SeleniumLauncher
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1315.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.2.2
> 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.
[jira] Assigned: (TAP5-1315) Allow individual SeleniumTestCases to
run w/o configuring SeleniumLauncher
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1315:
------------------------------------------
Assignee: Howard M. Lewis Ship
> 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
>
> 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.
[jira] Assigned: (TAP5-1315) Allow individual SeleniumTestCases to
run w/o configuring SeleniumLauncher
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1315:
------------------------------------------
Assignee: Howard M. Lewis Ship
> 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
>
> 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.
[jira] Commented: (TAP5-1315) Allow individual SeleniumTestCases to
run w/o configuring SeleniumLauncher
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922795#action_12922795 ]
Hudson commented on TAP5-1315:
------------------------------
Integrated in tapestry-5.2-freestyle #214 (See [https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/214/])
> 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.
[jira] Commented: (TAP5-1315) Allow individual SeleniumTestCases to
run w/o configuring SeleniumLauncher
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922795#action_12922795 ]
Hudson commented on TAP5-1315:
------------------------------
Integrated in tapestry-5.2-freestyle #214 (See [https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/214/])
> 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.
[jira] Commented: (TAP5-1315) Allow individual SeleniumTestCases to
run w/o configuring SeleniumLauncher
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ 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.