Re: Re: ExpectedException: expecting a cause's message

In the first instance I believe you're saying it's part of your
requirements that you output a useful message.  In this instance I would
test it but I would test the exception class directly and *not* the code
that uses it.  The code that uses it I would just test that the correct
exception has been raised.

In the second I would more than likely be wrapping the external exception
anyway so that it doesn't leak into *my* domain


On Wed, Jul 31, 2013 at 7:57 PM, mikecodeawesome <[email protected]> wrote:

> **
>
>
> Aha! I had a feeling there would be something like that already, I just
> didn't know where to find it. Thanks, I'll look into these suggestions.
>
> --- In [email protected], David Saff <saff@...> wrote:
> >
> > I think the ideal solution would be ...
>
>  
>



-- 
Maybe she awoke to see the roommate's boyfriend swinging from the
chandelier wearing a boar's head.

Something which you, I, and everyone else would call "Tuesday", of course.


[Non-text portions of this message have been removed]