Although --timer-warning/--timer-ok flags already provide the ability to highlight tests in a running time range, some tests have specific performance goals (specially integration tests). Additionally, sometimes, getting the console output in a target-remote environment is not trivial.
Given that, I proposed that nose-timer provide the ability to specify an upper bound time for each test. It could be accomplished by using annotations, as nose2dep does (image below)
We could have an annotation as:
@time_limit(value=15, unit='ms')
JoaoGFarias
commented
6 years ago
Feature request:
Although --timer-warning/--timer-ok flags already provide the ability to highlight tests in a running time range, some tests have specific performance goals (specially integration tests). Additionally, sometimes, getting the console output in a target-remote environment is not trivial.
Given that, I proposed that nose-timer provide the ability to specify an upper bound time for each test. It could be accomplished by using annotations, as nose2dep does (image below)
We could have an annotation as:
@time_limit(value=15, unit='ms')