Random test sometimes generates race condition like this:

2 breaks | 30ms initial idle timeout | t=10ms, t=140ms, t=270ms
expected 3 to equal 2

At t=270ms the function is called while it's time for a break. What is the expected behaviour here? If there's a specific desired behaviour then it should be tested in sample test; if not then it shouldn't be generated at all.

# Task talks about input changes as a firing condition. # Test seems to talk about firing simply on the function being called, and uses an entirely different function.

I think it'd be more clear if the given example used the same situation and function as specified earlier.

Also, examples are not specifications. Specifications of function input and "output" ( behaviour of the returned function ) should be given, with examples only clarifying the specified behaviour, not introducing additional specifications.

Also, separate the backstory from the task specification more clearly.