On Nov 26, 2009, at 5:08 AM, Mike Smith wrote: > Surely we should be setting up "other" tests to check that tests finish > executing within a certain time period.
Unfortunately, it has been my experience (at the time, with win32/VC++) that it's all too easy for the built-in unittest++ time limit guards to fail in cases when there is a single test which runs amok and modifies memory it shouldn't. A common result would be that some *random* number of tests *later* the entire process either (a) just exits quietly, with no core dump and no screen messages or (b) it never exits and can only be killed via the equivalent of SIGKILL. These scenarios would be extremely time consuming to figure out and offer one argument against "only show output when something fails" methodology. I'd opine that progress reporting of some kind is essential and ideally there are facilities to quickly zoom into the problem areas (which is what --suite and --include/exclude allow, among other things). Cheers, Vlad ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ unittest-cpp-devel mailing list unittest-cpp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel
