summaryrefslogtreecommitdiff
path: root/toxcore/mono_time_test.cc
diff options
context:
space:
mode:
authoriphydf <iphydf@users.noreply.github.com>2018-07-08 08:43:42 +0000
committeriphydf <iphydf@users.noreply.github.com>2018-07-09 21:04:50 +0000
commitabc17b0f8997ab07ae66130edd5dc8c43e72c886 (patch)
tree88056839c808a9f7f8c58f55ebe273aa7b5facdb /toxcore/mono_time_test.cc
parent4e21c065517d6e125cb1d1b9a13e886b3046b0d8 (diff)
Factor out time keeping code into its own module: mono_time.c.
It turns out, `unix_time` is also monotonic, and is used as such, so I've renamed the new functions to `mono_time_*`. 2018-07-08: ``` 00:01 <@irungentoo> the idea used to be that the unix_time() function could go backward in time but I think I might have started using it like if it could not after I changed it so that it would never go back in time ```
Diffstat (limited to 'toxcore/mono_time_test.cc')
-rw-r--r--toxcore/mono_time_test.cc30
1 files changed, 30 insertions, 0 deletions
diff --git a/toxcore/mono_time_test.cc b/toxcore/mono_time_test.cc
new file mode 100644
index 00000000..5ad91322
--- /dev/null
+++ b/toxcore/mono_time_test.cc
@@ -0,0 +1,30 @@
1#include "mono_time.h"
2
3#include <gtest/gtest.h>
4
5namespace {
6
7TEST(Util, UnixTimeIncreasesOverTime) {
8 unix_time_update();
9 uint64_t const start = unix_time();
10
11 while (start == unix_time()) {
12 unix_time_update();
13 }
14
15 uint64_t const end = unix_time();
16 EXPECT_GT(end, start);
17}
18
19TEST(Util, IsTimeout) {
20 uint64_t const start = unix_time();
21 EXPECT_FALSE(is_timeout(start, 1));
22
23 while (start == unix_time()) {
24 unix_time_update();
25 }
26
27 EXPECT_TRUE(is_timeout(start, 1));
28}
29
30} // namespace