Re: Testing exception safety

[Alf P. Steinbach]

On 9/27/2015 12:40 PM, Udo Steinbach wrote:
> After reading http://www.boost.org/community/exception_safety.html and
> experimenting with throwing at every point that can throw ...
> How do you test your code for exception safety?

You can use memory leak detectors to detect memory leaks. That's one aspect.

You can generate hashes of object state to detect changed object state.
That's another aspect.

These comments are just common sense. I'm not aware of special
techniques for generating exceptions within operations used by the code.
It could be very costly to create mockups of lower level operations.


> Is there any module for doing that in the world?

Don't know, sorry.

Cheers & hth.,

- Alf

[Ian Collins]

Udo Steinbach wrote:
> After reading http://www.boost.org/community/exception_safety.html
> and experimenting with throwing at every point that can throw ... How

> do you test your code for exception safety? Is there any module for

> doing that in the world?

As part of my unit tests, I mock everything the code under test calls.
It is straightforward to get the mock functions to throw exceptions.

--
Ian Collins

[Ian Collins]

Udo Steinbach wrote:
>> It could be very costly to create mockups of lower level
>> operations.
>

> What does Ian say on this? ("I mock everything the code under test
> calls") My variant is a macro which throws in DEBUG in combination
> with a class calling in some loops a test function until nothing is
> thrown and a list of allocated resources.

I use a framework that generates mock functions from an interface
description (basically a function prototype described in XML) so the
cost is low compared to the benefits.

--
Ian Collins