Property Result in case of exceptions about quickcheck-state-machine HOT 8 OPEN

What do you mean by "return a passing Result"?

from quickcheck-state-machine.

Also the equivalent NParallel.. commands may encounter executeCommands: impossible (for example when an exception during a MemoryReferene Create fails) because this #317 is not adopted yet.

Yes, we should implement the analogue of #317 for the NParallel... functions.

from quickcheck-state-machine.

What do you mean by "return a passing Result"?

The property doesn't fail

from quickcheck-state-machine.

The parallel property shouldn't necessarily fail if an exception is thrown on one of the threads. It should only fail if we cannot complete the history (#317) in any way that linearises.

Arguably we should either make runParallelCommands' (which completes histories) the default way to run the parallel property and remove runParallelCommands, or keep both runParallelCommands and runParallelCommands' and have runParallelCommands fail if there's any exception (since that function doesn't complete histories).

Is that what you meant or did you mean something else?

from quickcheck-state-machine.

Another way to think of it is that runParallelCommands should be used when there's no fault injection (exceptions), while runParallelCommands' should be used when there's fault injection.

from quickcheck-state-machine.

Yes, this is what I meant. I personally agree a bit more with the second option: make runParallelCommands fail on exceptions, since it doesn't complete histories.

from quickcheck-state-machine.

Another way to think of it is that runParallelCommands should be used when there's no fault injection (exceptions), while runParallelCommands' should be used when there's fault injection.

Yes exactly.

from quickcheck-state-machine.

I personally agree a bit more with the second option...

Yeah, I think you're right -- that's probably the better option.

from quickcheck-state-machine.