struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Turner" <tur...@blackbear.com>
Subject RE: Need help deciphering screw-case for PR 15799
Date Wed, 05 Feb 2003 06:48:24 GMT
> The other thing we all need to get better about is committing 
> test cases to the (currently pretty woeful) unit tests in 
> Struts, so that we can protect ourselves against regressions 
> later.  But I'm willing to forgo that for now, as long as we 
> (as a group) make it a high priority post-1.1 goal.


I have major problems (both for Struts and with my client's projects)
about regression testing, specifically with JSP.  This is really causing
problems for us in Struts, because many of the things that are coming up
are taglib-related and nearly impossible to accurately unit-test.

I'd love to see a good solution proposed for this, I've tried Cactus and
it's a good half-way step, but still doesn't really test the code on the
JSP page.

James Turner
Owner & Manager, Black Bear Software, LLC
turner@blackbear.com

Author: 
    MySQL & JSP Web Applications: 
        Data Driven Programming Using Tomcat and MySQL
    ISBN 0672323095; Sams, 2002

Co-Author: 
    Struts Kick Start
    ISBN 0672324725; Sams, 2002

Forthcoming:
    JavaServer Faces Kick Start 
    Sams, Fall 2003


> -----Original Message-----
> From: Craig R. McClanahan [mailto:craigmcc@apache.org] 
> Sent: Wednesday, February 05, 2003 1:40 AM
> To: Struts Developers List
> Subject: Re: Need help deciphering screw-case for PR 15799 
> 
> 
> 
> 
> On Wed, 5 Feb 2003, James Turner wrote:
> 
> > Date: Wed, 5 Feb 2003 00:52:21 -0500
> > From: James Turner <turner@blackbear.com>
> > Reply-To: Struts Developers List <struts-dev@jakarta.apache.org>
> > To: struts-dev@jakarta.apache.org
> > Subject: Need help deciphering screw-case for PR 15799
> >
> > I've taken a look at the code for 15799, but I'm still not exactly 
> > sure what problem was being reported.  I don't feel comfortable 
> > applying a patch for a problem that isn't properly 
> documented.  Anyone 
> > got a clue?
> >
> 
> Asking the initial bug reporter for a failure case (even if 
> it takes a direct email) is always good -- and it's 
> absolutely the right thing to do. If you can't prove that the 
> current code doesn't fail, you can't prove that any new code 
> succeeds.  Don't feel bad about closing it with WORKSFORME if 
> you can't reproduce it or acquire a test case.
> 
> The other thing we all need to get better about is committing 
> test cases to the (currently pretty woeful) unit tests in 
> Struts, so that we can protect ourselves against regressions 
> later.  But I'm willing to forgo that for now, as long as we 
> (as a group) make it a high priority post-1.1 goal.
> 
> Craig
> 
> > James Turner
> > Owner & Manager, Black Bear Software, LLC turner@blackbear.com
> >
> > Author:
> >     MySQL & JSP Web Applications:
> >         Data Driven Programming Using Tomcat and MySQL
> >     ISBN 0672323095; Sams, 2002
> >
> > Co-Author:
> >     Struts Kick Start
> >     ISBN 0672324725; Sams, 2002
> >
> > Forthcoming:
> >     JavaServer Faces Kick Start
> >     Sams, Fall 2003
> >
> >
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: struts-dev-help@jakarta.apache.org
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Mime
View raw message