From be6a765c69baf6f0bae77379438fb11c8f2c104a Mon Sep 17 00:00:00 2001 From: Paul Sokolovsky Date: Sun, 30 Oct 2016 21:33:12 +0300 Subject: [PATCH] tests/extmod/ticks_diff: Test for new semantics of ticks_diff(). --- tests/extmod/ticks_diff.py | 33 +++++++++++++++++++++++++++++++++ tests/extmod/ticks_diff.py.exp | 1 + 2 files changed, 34 insertions(+) create mode 100644 tests/extmod/ticks_diff.py create mode 100644 tests/extmod/ticks_diff.py.exp diff --git a/tests/extmod/ticks_diff.py b/tests/extmod/ticks_diff.py new file mode 100644 index 000000000..4d8df83cf --- /dev/null +++ b/tests/extmod/ticks_diff.py @@ -0,0 +1,33 @@ +from utime import ticks_diff, ticks_add + +MAX = ticks_add(0, -1) +# Should be done like this to avoid small int overflow +MODULO_HALF = MAX // 2 + 1 + +# Invariants: +# if ticks_diff(a, b) = c, +# then ticks_diff(b, a) = -c + +assert ticks_diff(1, 0) == 1, ticks_diff(1, 0) +assert ticks_diff(0, 1) == -1 + +assert ticks_diff(0, MAX) == 1 +assert ticks_diff(MAX, 0) == -1 + +assert ticks_diff(0, MAX - 1) == 2 + +# Maximum "positive" distance +assert ticks_diff(MODULO_HALF, 1) == MODULO_HALF - 1, ticks_diff(MODULO_HALF, 1) +# Step further, and it becomes a negative distance +assert ticks_diff(MODULO_HALF, 0) == -MODULO_HALF + +# Offsetting that in either direction doesn't affect the result +off = 100 +# Cheating and skipping to use ticks_add() when we know there's no wraparound +# Real apps should use always it. +assert ticks_diff(MODULO_HALF + off, 1 + off) == MODULO_HALF - 1 +assert ticks_diff(MODULO_HALF + off, 0 + off) == -MODULO_HALF +assert ticks_diff(MODULO_HALF - off, ticks_add(1, -off)) == MODULO_HALF - 1 +assert ticks_diff(MODULO_HALF - off, ticks_add(0, -off)) == -MODULO_HALF + +print("OK") diff --git a/tests/extmod/ticks_diff.py.exp b/tests/extmod/ticks_diff.py.exp new file mode 100644 index 000000000..d86bac9de --- /dev/null +++ b/tests/extmod/ticks_diff.py.exp @@ -0,0 +1 @@ +OK