tag:blogger.com,1999:blog-8341729382206275662.post5959834890908966859..comments2010-06-30T08:07:59.381-04:00Catherine Powellhttp://www.blogger.com/profile/15459370385548771048noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8341729382206275662.post-35452833315979498392010-06-30T07:01:51.033-04:002010-06-30T07:01:51.033-04:00And make sure that the error makes sense, don't just make it check for the error that happens to be generated.Assarnoreply@blogger.comtag:blogger.com,1999:blog-8341729382206275662.post-68605220084827917982010-06-28T11:21:18.592-04:002010-06-28T11:21:18.592-04:00That's really a programmer rule too, not just a testing rule. Try { something } catch (Exception e) { more code } is so so wrong! There's a reason you can subclass Exception.Tyler Breisacherhttp://www.blogger.com/profile/03197090819217016934noreply@blogger.com