Re: [Boost-users] Aborting on Boost.Test check failure

Jeremiah Willcock writes:

The code that I was working with uses a common test function that is called multiple times with different inputs, making it more difficult to breakpoint that single line. Is there a reason not to provide abort() or similar functionality?

Trunk version of Boost.Test provides a better (IMO) solution to this problem: test context. Using that you can see which input causes assertion to fail. Gennadiy