On Sun, Jun 29, 2008 at 9:41 AM, troy d. straszheim <troy@resophonic.com> wrote:
David Abrahams wrote:
troy d. straszheim wrote:

The test that causes this is just a program with a main() routine... It
seems like it should use boost.test, and boost.test should be
responsible for making these dialog-suppressing calls. (Does that sound
like it makes sense?)

1. I'm reluctant to recommend that any program use Boost.Test until its
documentation is made to correspond to its actual interface.

2. You'd better ask Gennadiy what makes sense for Boost.Test; I don't
understand the rationale by which it gets developed

3. Maybe we could have an option in boost/detail/lightweight_test, or
simply a separate header called boost/detail/regression.hpp that
includes something that does this.  Maybe the old
"dynamically-initialized static member of a template" trick makes sense
here.


Roger that, skipping to #3...

Before inventing something new, why not ask the Boost.Build folks how they suppress unwanted pop ups during Boost regression tests. They went through the exact same sequence you are now repeating; first a lot of popups occurred, then a few, then a few that closed automatically after some time, and finally none at all. That's regardless of whether the test involved is running under Boost.Test or not.

Also, are you aware Boost.Test already has the equivalent of "lightweight_test"? See trunk\boost\test\minimal.hpp.  If minimal.hpp is missing something, shouldn't the missing feature be added there rather inventing a whole new kind of lightweight test?

--Beman