Re: [boost] [Boost.Test] Assertion changes in trunk? [WAS: Call for Review: Boost.Test documentation rewrite]

Subject: Re: [boost] [Boost.Test] Assertion changes in trunk? [WAS: Call for Review: Boost.Test documentation rewrite]
From: Richard (legalize+jeeves_at_[hidden])
Date: 2014-01-23 23:27:15

[Please do not mail me a copy of your followup]

Alexander Lamaison <awl03_at_[hidden]> spake the secret code
<868uu8nv96.fsf_at_[hidden]> thusly:

>As 'CHECK' is the assertion level you should use by default, [...]

I don't know why you would say that when it is contrary to accepted
unit testing practices and the behavior of assertions in other
testing frameworks in every other language otu there.

For isntance, jUnit doesn't continue executing the test past the first
failed assertion.  Neither do unit testing frameworks in JavaScript or
Python or PHP, etc.

REQUIRE is the level you want by default, not CHECK.
-- 
"The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline>
     The Computer Graphics Museum <http://computergraphicsmuseum.org>
         The Terminals Wiki <http://terminals.classiccmp.org>
  Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>