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?
Thanks,
- Brendan
-----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 <[EMAIL PROTECTED]> 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]
