Subject: Re: [Boost-users] Aborting on Boost.Test check failure
From: Gennadiy Rozental (rogeeff_at_[hidden])
Date: 2012-03-06 05:21:07
Jeremiah Willcock <jewillco <at> osl.iu.edu> 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