>From: "CONNER, BRENDAN (SBCSI)" <[EMAIL PROTECTED]> > > OK, I'll look at that. But, out of curiosity, how is the Shale Test > Framework being used by people now? Is it being used mostly for > non-3-tier applications? What is the extent of the problem space in > which it is useful? (Obviously, it's not meant for stand-alone Java > J2SE applications, because then there would be no need for JSF support.) >
I would say that there is a percentage of folks that build applications that don't use EJB but still use good design patterns and are able to load-balance across several web containers without the complexity of EJB. For that cult, the Shale test framework would snap right in. If your application requires EJB, you Obviously have greater complexity to manage and more testing considerations. > Thanks, > > - Brendan > > -----Original Message----- > From: Gary VanMatre [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 16, 2006 11:31 AM > To: Struts Users Mailing List > Subject: RE: Re: [SHALE] Using the Test Framework > > > >From: "CONNER, BRENDAN (SBCSI)" > > > > Thanks for the info. I'm definitely interested in simplifying my > > testing strategy to the extent that it's possible, so any suggestions > > are welcome. In particular I'm trying to avoid having different > > versions of my delegates (one version that returns a dummy result and > > another that actually makes the call to the Session Bean doing the > > work), but I'm open to other ways of doing things. > > > > So how are people unit testing their JSF Action methods in a 3-tier > > application using the Shale Test Framework? Are they actually keeping > > around two different versions of their delegates to avoid having to do > > > the JNDI lookups? I'm open to altering my approach to fit the tool, > > provided I know what the recommended approach is. > > > > You might look at junitee (www.junitee.org). It allows you two run > junit test cases under the web container where you would have the JNDI > stuff. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
