summaryrefslogtreecommitdiffstats
path: root/src/scripttools
diff options
context:
space:
mode:
authorThiago Macieira <thiago.macieira@nokia.com>2011-03-21 09:39:49 (GMT)
committerThiago Macieira <thiago.macieira@nokia.com>2011-03-22 14:51:22 (GMT)
commite4b41ca2f9aec1be1136decbac323e024f64a176 (patch)
treeb37f4646642743f4ac0920906d73d2a0f49c2690 /src/scripttools
parentbef9fe90beb33e10bcfa03ecee4062b8d9f642ff (diff)
downloadQt-e4b41ca2f9aec1be1136decbac323e024f64a176.zip
Qt-e4b41ca2f9aec1be1136decbac323e024f64a176.tar.gz
Qt-e4b41ca2f9aec1be1136decbac323e024f64a176.tar.bz2
Add a feature to QTestLib to correct benchmark results.
Two special values are added to the measurement of benchmarks: a zero and a comparison. The "zero" value is to be used when the test incurs a non-negligible overhead just to run. The benchmark author should add an "empty" run that measures basically the overhead and set it to attribute QTest::Zero. The "zero" value will be subtracted from any benchmark measurements before reporting (currently the plain logger only). Note that all benchmark types don't make sense, notably those already measurement some kind of rate, like frames per second and bytes per second. The "baseline" value is the comparison (with the "zero" subtracted"). When the baseline is set, the library will instead report the ratio between the benchmark and the baseline, in percentage or a multiple (e.g. "75%" [of the time] or "10.0x" [faster]). Adding measurements in "robes" left for future improvement. This feature is not reviewed and will be reverted later.
Diffstat (limited to 'src/scripttools')
0 files changed, 0 insertions, 0 deletions