Software /
code /
prosody
Annotate
spec/util_time_spec.lua @ 9309:33d500c25d76
net.server_epoll: Refactor Direct TLS assumptions outwards
The assumption that connections are "Direct TLS" when a TLS context is
supplided should be broken. The goal is to make it easy to add a new API
that can be given a TLS context at creation even if it should do
STARTTLS.
With this commit, only the exposed server_select-compatible API assumes
Direct TLS when a TLS context is included.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Thu, 13 Sep 2018 20:37:43 +0200 |
parent | 9193:aba99b6539f5 |
rev | line source |
---|---|
9193 | 1 describe("util.time", function () |
2 local time; | |
3 setup(function () | |
4 time = require "util.time"; | |
5 end); | |
6 describe("now()", function () | |
7 it("exists", function () | |
8 assert.is_function(time.now); | |
9 end); | |
10 it("returns a number", function () | |
11 assert.is_number(time.now()); | |
12 end); | |
13 end); | |
14 describe("monotonic()", function () | |
15 it("exists", function () | |
16 assert.is_function(time.monotonic); | |
17 end); | |
18 it("returns a number", function () | |
19 assert.is_number(time.monotonic()); | |
20 end); | |
21 it("time goes in one direction", function () | |
22 local a = time.monotonic(); | |
23 local b = time.monotonic(); | |
24 assert.truthy(a <= b); | |
25 end); | |
26 end); | |
27 end); | |
28 | |
29 | |
30 | |
31 |