The point wasn't how long it took. The point was how much stuff there was to sift through.
Say you run 10000 tests, and test 5849 fails. With all of that output, how do you know what failed? On Mon, Nov 23, 2009 at 6:28 AM, Vlad <v...@demoninsight.com> wrote: > > unittest>time ./TestUnitTest++ > Success: 175 tests passed. > Test time: 0.09 seconds. > real 0m0.120s > user 0m0.007s > sys 0m0.005s > > unittest>time ./alltests > ... > real 0m0.127s > user 0m0.011s > sys 0m0.009s > Even with a pessimistic estimate of ~ 1ms overhead per 1 line of console > output, each 1000 tests add ~2 sec to the testing time. Hopefully that's > negligible compared to what all those tests really do .... ------------------------------------------------------------------------------ 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
