Tapestry 5
  1. Tapestry 5
  2. TAP5-758

Move TapestryTestConstants from tapestry-test into tapestry-core, so that non-selenium test code does not need to use tapestry-test

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 5.1.0.5
    • Fix Version/s: None
    • Labels:
      None

      Description

      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.

        Activity

          People

          • Assignee:
            Igor Drobiazko
            Reporter:
            Paul Field
          • Votes:
            3 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development