Beehive
  1. Beehive
  2. BEEHIVE-103

JUnit test support for controls in standalone environment

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: V1Alpha, V1Beta, v1m1
    • Fix Version/s: 1.0.1
    • Component/s: Controls
    • Labels:
      None

      Description

      A set of classes have been developed that allows for the definition of JUnit test
      cases to be able to run in a 'standalone' bean context container or within a j2ee
      or servlet container in a transparent fashion. The contract is simply that the test
      case inherit from one of two base classes ControlTestCase or SingleControlTestCase.

      1. junit-control.zip
        4 kB
        C Brett Bennett

        Activity

        Hide
        matt c added a comment -

        Verified that the test controls framework was added to beehive (quite awhile ago). Tests are actively being run using this framework.

        Show
        matt c added a comment - Verified that the test controls framework was added to beehive (quite awhile ago). Tests are actively being run using this framework.
        Hide
        Eddie O'Neil added a comment -

        Controls test container added in SVN 356071. Needs Forrest doc, Javadoc, and a sample, but the code is in place.

        Show
        Eddie O'Neil added a comment - Controls test container added in SVN 356071. Needs Forrest doc, Javadoc, and a sample, but the code is in place.
        Hide
        Eddie O'Neil added a comment -

        The scope of the bug is to ship (to Beehive users) a standalone controls test environment that can be used to host arbitrary controls testing. The classes currently being used in the EJB, JMS, and web service controls aren't sufficient to meet these needs (IMHO) as they don't provide the flexibility that's needed by the test author to subclass / delegate, extend the container context, etc.

        IMHO, until the feature set is delivered, this bug needs to remain open as the goal (delivering this to users) hasn't quite been met yet.

        Unfortunately, this won't make it into Beehive 1.0 as I've not had enough time yet to port some of the controls tests to use the new container and thus it's not entirely validated yet...

        Should happen right after we ship Beehive 1.0.

        Show
        Eddie O'Neil added a comment - The scope of the bug is to ship (to Beehive users) a standalone controls test environment that can be used to host arbitrary controls testing. The classes currently being used in the EJB, JMS, and web service controls aren't sufficient to meet these needs (IMHO) as they don't provide the flexibility that's needed by the test author to subclass / delegate, extend the container context, etc. IMHO, until the feature set is delivered, this bug needs to remain open as the goal (delivering this to users) hasn't quite been met yet. Unfortunately, this won't make it into Beehive 1.0 as I've not had enough time yet to port some of the controls tests to use the new container and thus it's not entirely validated yet... Should happen right after we ship Beehive 1.0.
        Hide
        Jeremiah Johnson added a comment -

        I am curious about the scope of this bug. It looks like the attached classes (junit-control.zip) are used in the EJB and JMS system-control samples; by being there, perhaps the scope of this bug can be considered resolved?

        Show
        Jeremiah Johnson added a comment - I am curious about the scope of this bug. It looks like the attached classes (junit-control.zip) are used in the EJB and JMS system-control samples; by being there, perhaps the scope of this bug can be considered resolved?
        Hide
        Eddie O'Neil added a comment -

        Changing this to a feature; it's not really about adding a test.

        Show
        Eddie O'Neil added a comment - Changing this to a feature; it's not really about adding a test.
        Hide
        Kyle Marvin added a comment -

        Eddie is going to take a look at this... in addition to the attached version, there is one in the controls test dir plus several other ad hoc ones floating around.

        Clealy a demand for this...

        Show
        Kyle Marvin added a comment - Eddie is going to take a look at this... in addition to the attached version, there is one in the controls test dir plus several other ad hoc ones floating around. Clealy a demand for this...
        Hide
        Dan Diephouse added a comment -

        These look very good. A lot like the stuff I did for BEEHIVE-89 (which can be marked as closed once this stuff goes in), but better . I'm not sure I understand why there is the SingleControlTestCase though...

        Show
        Dan Diephouse added a comment - These look very good. A lot like the stuff I did for BEEHIVE-89 (which can be marked as closed once this stuff goes in), but better . I'm not sure I understand why there is the SingleControlTestCase though...

          People

          • Assignee:
            matt c
            Reporter:
            C Brett Bennett
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development