You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Igor Drobiazko (JIRA)" <ji...@apache.org> on 2009/12/15 08:26:18 UTC
[jira] Assigned: (TAP5-758) Move TapestryTestConstants from
tapestry-test into tapestry-core, so that non-selenium test code does not
need to use tapestry-test
[ https://issues.apache.org/jira/browse/TAP5-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Drobiazko reassigned TAP5-758:
-----------------------------------
Assignee: Igor Drobiazko
> Move TapestryTestConstants from tapestry-test into tapestry-core, so that non-selenium test code does not need to use tapestry-test
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-758
> URL: https://issues.apache.org/jira/browse/TAP5-758
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core, tapestry-test
> Affects Versions: 5.1.0.5
> Reporter: Paul Field
> Assignee: Igor Drobiazko
>
> The tapestry-test module is meant to be "just a couple of base classes to make it easier to build integration test suites around Selenium.".
> However, org.apache.tapestry5.internal.test.PageTesterContext for tapestry-core uses TapestryTestConstants from tapestry-test. So it seems that anyone doing any kind of tests requires the tapestry-test module and so also imports all the selenium dependencies.
> That dependency problem could be resolved by moving TapestryTestConstants into tapestry-core.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.