summaryrefslogtreecommitdiff
path: root/test/parallel/test-timers-next-tick.js
diff options
context:
space:
mode:
Diffstat (limited to 'test/parallel/test-timers-next-tick.js')
-rw-r--r--test/parallel/test-timers-next-tick.js15
1 files changed, 15 insertions, 0 deletions
diff --git a/test/parallel/test-timers-next-tick.js b/test/parallel/test-timers-next-tick.js
new file mode 100644
index 0000000000..1db1d18c3a
--- /dev/null
+++ b/test/parallel/test-timers-next-tick.js
@@ -0,0 +1,15 @@
+'use strict';
+
+const common = require('../common');
+
+// This test documents an internal implementation detail of the Timers:
+// since timers of different durations are stored in separate lists,
+// a nextTick queue will clear after each list of timers. While this
+// behaviour is not documented it could be relied on by Node's users.
+
+setTimeout(common.mustCall(() => {
+ process.nextTick(() => { clearTimeout(t2); });
+}), 1);
+const t2 = setTimeout(common.mustNotCall(), 2);
+
+common.busyLoop(5);