Boost C++ Libraries: Ticket #7082: Add support for benchmarking https://svn.boost.org/trac10/ticket/7082 <p> One useful thing with boost test would be to run the tests in a "benchmarking mode". The general idea is to be able to run many iterations of all tests to get an idea of their performance. I believe the following changes would be sufficient: </p> <ul><li>BOOST_AUTO_TEST_CASE could have an additional optional parameter: number_of_iterations. This is set by the user manually. For example: BOOST_AUTO_TEST_CASE(my_test_case, 10000). If not passed in, it would default to 1. </li><li>A new command line parameter would trigger benchmarking: say --benchmarking. When passed in, all tests would run number_of_ iterations times. </li><li>the elapsed time for a test would then be the accumulated time taken by all iterations </li></ul><p> This would be great for nightlies. </p> <p> This issue was discussed a bit on the mailing-list on this thread: </p> <p> <a class="ext-link" href="http://lists.boost.org/boost-users/2011/01/65790.php"><span class="icon">​</span>http://lists.boost.org/boost-users/2011/01/65790.php</a> </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/7082 Trac 1.4.3 marco.craveiro@… Tue, 31 Jul 2012 15:38:08 GMT <link>https://svn.boost.org/trac10/ticket/7082#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/7082#comment:1</guid> <description> <p> It just occurred me that, as a side effect, setting number_of_iterations to zero is also a great way of ignoring tests. However, Gennadiy has stated there is already a solution for this particular problem: </p> <p> <a class="ext-link" href="http://lists.boost.org/boost-users/2012/07/75075.php"><span class="icon">​</span>http://lists.boost.org/boost-users/2012/07/75075.php</a> </p> </description> <category>Ticket</category> </item> </channel> </rss>