Boost Testing :
From: Victor A. Wagner Jr. (vawjr_at_[hidden])
Date: 2005-04-14 00:12:34
At Wednesday 2005-04-13 20:37, you wrote:
>I'm noticing the betweenness_centrality_test takes more than 14 minutes to
>run (Athlon 1400).
>We need some way of profiling the tests as long as we don't have a way of
>limiting the execution time for them. Apparently, a couple of the tests
>take quite long to run and I only can find them out by staring at the
>screen while the tests are running. While excessive time consumption at
>first only annoys the testers, it also may indicate a flaw in the code.
>The amount of time (and RAM) consumed actually is important information.
Martin, it _should_ be rather easy to add a timestamp to the test logs each
time a test is run.
I wrote a very small application using boost::date-time which produces:
C:\Documents and Settings\vawjr>timestamp
adding the actual code (basically format the current time) should be
trivial for any booster
as for the memory usage, could be tricky on windows.
>Boost-Testing mailing list
Victor A. Wagner Jr. http://rudbek.com
The five most dangerous words in the English language:
"There oughta be a law"