That'd be nice. I'm looking at using boost.test for some of my application-specific unit tests, but these kinds of practical issues get in the way, to wit: - passing test configuration - listing the tests contained in the unit test (so that I can compare the tests run against the total number of tests available - hard to know how much coverage you're getting if you don't know what's in the .exe) - "expected failure" feature - the ability to generate a better error message - ie, include a bit of text about what the test was about. Cheers, Rob. "Gennadiy Rozental" <gennadiy.rozental@thomson.com> wrote in message news:d2u7ic$iam$1@sea.gmane.org...
"Robert Mathews" <rmathews@envoyww.com> wrote in message news:d2u5g9$aiv$1@sea.gmane.org...
AFAIT, there is also no way to pass configuration data into BOOST test either. For example, some unit tests might need the name of an account
to
run under, or the name of an existing share, or some such site-specific configuration. I'd like the ability to pass in a set of name-value pairs to rectify that. Maybe, --configfile <xmlfile>
Rob.
Don't hold your breath, but I may be able to present something like this in near future.
Gennadiy