Terrible error message from throws matcher

[npryce]

No description provided.

[charleskorn]

Not sure if this is the same thing or not, but it would be great if the throws() matcher could include details of the exception if it doesn't match the expected type. At the moment, if the expectation is for say a FileNotFoundException, but a ArgumentException is thrown instead, all the error message gives you is the type of the actual exception (ArgumentException) with no further details. Including details like the message and stack trace would be very helpful.