
Gennadiy Rozental writes:
"Dave Steffen" <dgsteffen@numerica.us> wrote in message news:17874.15059.105215.467627@yttrium.numerica.us...
Yep. That's the reason expected failures usage should be limited.
Well, yes. In fact, I'm curious about your use cases for expected failures. What do you think it means for a failure to be expected?
In my own test modules I don't use it at all. But than here at wark we don't have well esteblished regression testing.
:-) Well, OK then. The only thing _we_ are using it for is to mark old (e.g. pre-Boost Test) hopelessly broken unit tests, and to mark code that should have unit tests but doesn't. I'm in charge of a new project, just starting up, which will get an entirely new code base; I don't plan to have any either. It's good to know I'm not crazy, or missing something obvious.
Ah... we're in the process of moving to 1.33.1 right now. (We have to do regression tests, etc.) We'll go to 1.34 when it comes out, unless it's seriously delayed... hmm... [comments snipped] :-)
I recommend you to try to use 1.34 RC even if it is Boost.Test only. My guess it should work even when compiled in 1.33.1 environment.
I'll look in to it. We don't have huge processes around here for putting different library versions in to use, but there's a little futzing. :-) I do like the notion of fixtures... ---------------------------------------------------------------------- Dave Steffen, Ph.D. Software Engineer IV Disobey this command! Numerica Corporation ph (970) 461-2000 x227 fax (970) 461-2004 - Douglas Hofstadter dgsteffen@numerica.us ___________________ Numerica Disclaimer: This message and any attachments are intended only for the individual or entity to which the message is addressed. It is proprietary and may contain privileged information. If you are neither the intended recipient nor the agent responsible for delivering the message to the intended recipient, you are hereby notified that any review, retransmission, dissemination, or taking of any action in reliance upon, the information in this communication is strictly prohibited, and may be unlawful. If you feel you have received this communication in error, please notify us immediately by returning this Email to the sender and deleting it from your computer.