CPAN version Build Status Coverage Status


Test::Timer - test module to test/assert response times


The documentation in this module describes version 0.18 of Test::Timer


use Test::Timer;

time_ok( sub { doYourStuffButBeQuickAboutIt(); }, 1, 'threshold of one second');

time_atmost( sub { doYourStuffYouHave10Seconds(); }, 10, 'threshold of 10 seconds');

time_between( sub { doYourStuffYouHave5-10Seconds(); }, 5, 10,
    'lower threshold of 5 seconds and upper threshold of 10 seconds');

#Will succeed
time_nok( sub { sleep(2); }, 1, 'threshold of one second');

time_atleast( sub { sleep(2); }, 2, 'threshold of one second');

#Will fail after 5 (threshold) + 2 seconds (default alarm)
time_ok( sub { while(1) { sleep(1); } }, 5, 'threshold of one second');

$test::Timer::alarm = 6 #default 2 seconds

#Will fail after 5 (threshold) + 6 seconds (specified alarm)
time_ok( sub { while(1) { sleep(1); } }, 5, 'threshold of one second');


Test::Timer implements a set of test primitives to test and assert test times from bodies of code.

The key features are subroutines to assert or test the following:


Test::Timer exports:



Takes the following parameters:

If the execution of the code exceeds the threshold the test fails


The is the inverted variant of time_ok, it passes if the threshold is exceeded and fails if the benchmark of the code is within the specified timing threshold.

The API is the same as for time_ok.

time_nok( sub { sleep(2); }, 1, 'threshold of one second');


This is syntactic sugar for time_ok

time_atmost( sub { doYourStuffButBeQuickAboutIt(); }, 1, 'threshold of one second');


time_atleast( sub { sleep(2); }, 1, 'threshold of one second');

The test succeeds if the code takes at least the number of seconds specified by the timing threshold.

Please be aware that Test::Timer, breaks the execution with an alarm specified to trigger after the specified threshold + 2 seconds, so if you expect your execution to run longer, set the alarm accordingly.

$Test::Timer::alarm = $my_alarm_in_seconds;

See also diagnostics.


This method is a more extensive variant of time_atmost and time_ok, you can specify a lower and upper threshold, the code has to execute within this interval in order for the test to succeed

time_between( sub { sleep(2); }, 5, 10,
    'lower threshold of 5 seconds and upper threshold of 10 seconds');



This is a method to handle the result from _benchmark is initiates the benchmark calling benchmark and based on whether it is within the provided interval true (1) is returned and if not false (0).


This is a simpler variant of the method above, it is the author’s hope that is can be refactored out at some point, due to the similarity with _runtest.


This is the method doing the actual benchmark, if a better method is located this is the place to do the handy work.

Currently Benchmark is used. An alternative could be Devel::Timer, but I do not know this module very well and Benchmark is core, so this is used for now.

The method takes two parameters:


This is the method extracts the seconds from benchmarks timestring and returns it as an integer.

It takes the timestring from _benchmark (Benchmark) and returns the seconds part.


Test::Builder required import to do some import hokus-pokus for the test methods exported from Test::Timer. Please refer to the documentation in Test::Builder


All tests either fail or succeed, but a few exceptions are implemented, these are listed below.


This module requires no special configuration or environment.

Tests are sensitive and be configured using environment and configuration files, please see the section on test and quality.



This module holds no known incompatibilities.


This module holds no known bugs.

The current implementations only use seconds and resolutions should be higher, so the current implementation is limited to seconds as the highest resolution.

On occassion failing tests with CPAN-testers have been observed. This seem to be related to the test-suite being not taking into account that some smoke-testers do not prioritize resources for the test run and that addional processes/jobs are running. The test-suite have been adjusted to accomodate this but these issues might reoccur.


Coverage Status

Coverage report for the release described in this documentation (see VERSION).

---------------------------- ------ ------ ------ ------ ------ ------ ------
File                           stmt   bran   cond    sub    pod   time  total
---------------------------- ------ ------ ------ ------ ------ ------ ------
blib/lib/Test/Timer.pm         91.7   93.8   66.7   88.5  100.0   99.9   90.7
...Timer/TimeoutException.pm  100.0    n/a    n/a  100.0  100.0    0.1  100.0
Total                          93.1   93.8   66.7   90.6  100.0  100.0   92.1
---------------------------- ------ ------ ------ ------ ------ ------ ------

The Test::Perl::Critic test runs with severity 5 (gentle) for now, please refer to t/critic.t and t/perlcriticrc.

Set TEST_POD to enable Test::Pod test in t/pod.t and Test::Pod::Coverage test in t/pod-coverage.t.

Set TEST_CRITIC to enable Test::Perl::Critic test in t/critic.t


This distribution uses Travis for continuous integration testing, the Travis reports are public available.

Build Status



Please report any bugs or feature requests either using Github


You can find (this) documentation for this module with the perldoc command.

perldoc Test::Timer

You can also look for information at:





Test::Timer and related modules are (C) by Jonas B. Nielsen, (jonasbn) 2007-2017

Test::Timer and related modules are released under the Artistic License 2.0

Used distributions are under copyright of there respective authors and designated licenses

Image used on website is under copyright by Veri Ivanova