Multiple stubbings with throwException causes unexpected behavior

[dindy]

When you set two stubbings that match the same invocation with the first stubbing calling throwException declaring the second stubbing trigger the exception of the first stubbing.

Example :

td.when(dep()).thenThrow(new Error())
td.when(dep()).thenReturn(true)

Executing the above code will throw an error of type Error.

I think it relates to this issue. Not sure if it can be fixed in testdouble but is there at least a workaround ?

[searls]

Apologies, but it has been quite a long time since the last release of testdouble so I generally consider the behavior plus API to be locked at this point.

In general, when two stubbings are satisfied, it should indeed be last-in-wins (as one expects more specific conditions to be introduced later in a given test), however, there is clearly a bug where stubbings are triggered on a first-in wins basis. My recommendation would be to avoid doing this, even if it means branching inside the test.