Hi David, >From the end user point of view (at least in my company), that would be great to consider a test case as a no-interface view bean or so.
Basically, they need to be able to inject resources, EJBs, ... as if they were in a stateless for example. The point I mean is transactions! De we need to deal with transactions in TestCases? IMO, no! Either way, they need something simple to increase productivity. Quintin's proposal was AFAIC simple. Your testcase is also very useful but it targets advanced people if they want to build their own application/module, ... (very useful to build our testcases for example) I would be in favor of pushing something basic and simple and wait for some feedback of the community. IMHO, it's simpler to push something simple and enhance it afterwards, than pushing something more complex/feature-full and having to break something in next releases. Jean-Louis -- View this message in context: http://openejb.979440.n4.nabble.com/Re-JUnit-Runner-0-1-tp988903p3042736.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
