NextThought / nti.testing / 56

100%

Pull #6

travis-ci

Make time_monotonically_increases safer

- It always increases even across functions.
- It doesn't start at 0 but the current time.

Note that because it goes across functions it can increase rapidly,
meaning that the real clock can start to get behind, which may not be
ideal. Two things are provided to address this:

* a ``granularity`` argument to slow down the growth. We stay at 1.0
  for backwards compatibility.
* A reset_monotonic_time(value) that can be used to either take the
  clock back to the current time or set it in the past for a set
  number of seconds. This can be useful in teardown functions.

Add lots of tests for this, and some docs.

32 of 32 new or added lines in 5 files covered. (100.0%)

473 of 477 relevant lines covered (99.16%)

4.94 hits per line