>From: "CONNER, BRENDAN (SBCSI)" <[EMAIL PROTECTED]> > > OK. We're working with IBM's RSA IDE (which uses Eclipse underneath). > I'm just trying to fit into my mind how to organize the two root source > directories in that environment. We have a Web Project set up that > contains the application code to be tested. Normally, we just export > our application (including a J2EE Application project, which refers to > Web Project(s), EJB project(s), and Java Utility project(s)) to an EAR > file for deployment to the server, but we didn't want the test framework > stuff to be part of that export. >
A new feature to RSA (I guess new to eclipse 3.x) is the ability to create links outside of a project. This is pretty handy for linking in source folders that are not under a project. Pull up the properties for a web project and select "Java Build Path" and the "Source" tab, and then click on the "add folder" button. Select the project root folder and click "create new folder" (only works for the root folder). Use the "advanced" button to link in a source folder. This is also an option for folders but it doesn't seem to work for the WebContent using just eclipse (haven't tried it under RAD). You might try adding the test source folder to your web project and then just exclude it from the build path using the source tab. Then create a test project that has links to the source in the other project. To make this work on multiple workstations I think you would need to use a link variable instead of a path. I'm sure there are several other options. You might look at the "Project Reference" too. Gary > - Brendan > > -----Original Message----- > From: Gary VanMatre [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 14, 2006 10:42 AM > To: Struts Users Mailing List > Subject: RE: [SHALE] Using the Test Framework > > > >From: "CONNER, BRENDAN (SBCSI)" > > > > OK, I'm going through the section in the PDF document ("Shale > Framework > > v.1.0.1-SNAPSHOT Project Documentation") on the Test Framework. In > that > > section, the example appears to involve creating a test class > > (SelectTestCase) in the same WAR project as the application code. Is > > this true? If so, how can we cleanly omit the test case code and > > infrastructure during deployment? Is there posted example code on the > > Web of a completed test case so I can see where everything was placed? > > > > > The shale test framework provides mock objects for junit testing outside > of a web container. The projects are generally organized with two root > source directories. One for your application source and the other for > automated testing. > > The shale framework nightly > (http://svn.apache.org/builds/struts/nightly/struts-shale/) archive > contains a "test-framework" folder that has a blank project structure > including an ant build. > > > > Thanks, > > > > - Brendan > > > > Gary > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Craig > > McClanahan > > Sent: Friday, February 10, 2006 5:43 PM > > To: Struts Users Mailing List > > Subject: Re: [SHALE] Using the Test Framework > > > > > > On 2/10/06, Craig McClanahan wrote: > > > > > > The only classes in shale-test.jar that depend on the rest of Shale > is > > the > > > convenience base classes in the org.apache.shale.test.base package. > > The > > > mock object classes have no dependencies on Shale, so you're welcome > > > to use > > > them to support general JSF based development activities. > > > > > > > Actually, I need to refine this a little. The base class > > AbstractViewControllerTestCase is the only one that assumes a Shale > API > > (ViewController in this case). AbstractJsfTestCase assumes only the > > standard JSF, Servlet, and JSP APIs, making it tremendously useful for > > > testing pretty much any part of a JSF application, because it wires > > together > > FacesContext and all the other pieces for you. > > > > > > Craig > > > > > > > > Craig > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
