[ http://issues.apache.org/jira/browse/BEEHIVE-103?page=comments#action_12320061 ]
Eddie O'Neil commented on BEEHIVE-103: -------------------------------------- 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. > JUnit test support for controls in standalone environment > --------------------------------------------------------- > > Key: BEEHIVE-103 > URL: http://issues.apache.org/jira/browse/BEEHIVE-103 > Project: Beehive > Type: New Feature > Components: Controls > Versions: V1Alpha, V1Beta, v1m1 > Reporter: C Brett Bennett > Assignee: Eddie O'Neil > Priority: Minor > Fix For: TBD > Attachments: junit-control.zip > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
