orSkip and throwing exceptions

[Robin Green]

I had a strange issue last week in which it seemed orSkip was being
ignored, no matter where I put it. I think this was because I was
using a mutable specification, in which, by default, match failures
throw exceptions. It would be nice if this mistake (trying to use
orSkip in conjunction with matchers that throw exceptions) could be
made more obvious somehow - and in any case, I think it should be
mentioned when "orSkip" is talked about in the documentation.

[etorreborre]

A precise example would be interesting.

I just had a look at the "orSkip" code and it looks like failure are intercepted ok but not errors. Is that errors you're having which should be skipped?

Thanks,

Eric.

[Robin Green]

I don't have the code in front of me right now because I'm not at work
- I can check it next week - but I think it was because the failing
matcher threw an exception, so .orSkip was never reached at all, so it
could not possibly have any effect.

[etorreborre]

Hi Robin, 

You can try the latest 1.12.2-SNAPSHOT where the matchers are more robusts when using "orSkip" or "orPending".

Thanks,

Eric.

[Daniel Sobral]

On Tue, Oct 2, 2012 at 7:47 PM, etorreborre <etorr...@gmail.com> wrote:
> Hi Robin,
>
> You can try the latest 1.12.2-SNAPSHOT where the matchers are more robusts
> when using "orSkip" or "orPending".

Where are orSkip and orPending in the documentation? I don't recall
ever seeing them.

--
Daniel C. Sobral

I travel to the future all the time.

[etorreborre]

They are buried into this big paragraph showing all the ways to create custom matchers from existing ones:

http://etorreborre.github.com/specs2/guide/org.specs2.guide.Matchers.html#Custom

E.