Comments in line. > -----Original Message----- > From: Joe Germuska [mailto:[EMAIL PROTECTED] > Sent: Monday, December 8, 2003 09:56 PM > To: 'Struts Developers List' > Subject: Test Case Exception Throwing style (Re: Cactus tests)
> I would suggest that the proper behavior here is to throw the exception > and let JUnit deal with it as an error rather than a failure. This > puts the actual error in the test report, which makes it a lot easier > to solve the problem. +1 sounds good. > For what it's worth, I've got it passing 71/97 tests clear, and the > rest fall into two categories: 19 with failures because the > context-path of the test app is hardcoded as "test" and the plugin uses > "struts-cactus", and 7 that have to do with cookie values. If anyone > has any clever ideas for the simplest way to extract the context path The context path used for the test is stored in the build.properties file. Couldn't those properties be read in by the unit tests ? Right now they are used to modify the server.xml file by using ant filtering while copying. Also if you look at the CVS history of those files with a hard coded 'test' context you'll probably see the path change from /test/xyz/abc.jsp -> /xyz/abc.jsp -> /test/xyz/abc.jsp Why this occured I couldn't tell you. > without using the tags which are being tested, I'm all ears... the > cookie thing is totally baffling at the moment. > > Joe > > > -- > Joe Germuska > [EMAIL PROTECTED] > http://blog.germuska.com > "We want beef in dessert if we can get it there." > -- Betty Hogan, Director of New Product Development, National > Cattlemen's Beef Association > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
