Tapestry 5
  1. Tapestry 5
  2. TAP5-1036

It would be nice if there was a way for committers to run individual integration tests again

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: 5.2
    • Fix Version/s: 5.2.0
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      Since the refactoring of the integration tests into several classes, it's not possible to run individual integration tests anymore. This is annoying when working on an issue where you want one or two tests to be run but not the whole suite.

        Issue Links

          Activity

          Hide
          Howard M. Lewis Ship added a comment -

          I created testng-limited.xml as a placeholder for running a subset of the integration tests.

          Show
          Howard M. Lewis Ship added a comment - I created testng-limited.xml as a placeholder for running a subset of the integration tests.
          Hide
          Ulrich Stärk added a comment -

          I'm still not satisfied with that. The only problem prohibiting it to be run individually from Eclipse's or IDEA's testng integration that I see is that SeleniumTestCase needs to be provided with a web app folder. This normally comes from the testng.xml.

          I propose adding an annotation @WebAppFolder to tapestry-test with which developers can specify the web app folder in which this test class should run on a per-class basis. SeleniumTestCase will be changed to look for the presence of this annotation and if present, use the value provided there. Otherwise it would take the value from the xml config file or fall back to the default of src/test/webapp.

          Thoughts?

          Show
          Ulrich Stärk added a comment - I'm still not satisfied with that. The only problem prohibiting it to be run individually from Eclipse's or IDEA's testng integration that I see is that SeleniumTestCase needs to be provided with a web app folder. This normally comes from the testng.xml. I propose adding an annotation @WebAppFolder to tapestry-test with which developers can specify the web app folder in which this test class should run on a per-class basis. SeleniumTestCase will be changed to look for the presence of this annotation and if present, use the value provided there. Otherwise it would take the value from the xml config file or fall back to the default of src/test/webapp. Thoughts?

            People

            • Assignee:
              Ulrich Stärk
              Reporter:
              Ulrich Stärk
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development