That's a good suggestion. Same should happen for intercept. I'll try
and add that to the upcoming 1.8 release.
Thanks.
Bill
> --
> You received this message because you are subscribed to the Google
> Groups "scalatest-users" group.
> To post to this group, send email to scalate...@googlegroups.com
> To unsubscribe from this group, send email to
> scalatest-use...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/scalatest-users?hl=en
> ScalaTest itself, and documentation, is available here:
> http://www.artima.com/scalatest
--
Bill Venners
Artima, Inc.
http://www.artima.com
The problem here was actually that I wasn't including the thrown
exception as the TestFailedException's cause when using the
"eventually ... should produce" syntax. This is what I had been doing
in intercept all along. The current 1.8-SNAPSHOT fixes this. Please
give the new 1.8-SNAPSHOT a try and let me know if this works for you.
https://oss.sonatype.org/content/groups/public/org/scalatest/
Thanks.
Bill
On Wed, Mar 14, 2012 at 1:43 PM, Martin Pärtel <martin...@gmail.com> wrote:
On 04/08/2012 01:46 AM, Bill Venners wrote:
> Hi Martin,
>
> The problem here was actually that I wasn't including the thrown
> exception as the TestFailedException's cause when using the
> "eventually ... should produce" syntax. This is what I had been doing
> in intercept all along. The current 1.8-SNAPSHOT fixes this. Please
> give the new 1.8-SNAPSHOT a try and let me know if this works for you.
>
> https://oss.sonatype.org/content/groups/public/org/scalatest/
>
> Thanks.
>
> Bill
>