From 2bfa6a56841e8a7fcf4ee28e6673ad1e1ff23360 Mon Sep 17 00:00:00 2001 From: Adam Gastineau Date: Fri, 6 Dec 2024 11:27:32 -0800 Subject: [PATCH] Add undefined behavior clarity --- docs/src/clock.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/clock.md b/docs/src/clock.md index 8c824eb264..44582f450b 100644 --- a/docs/src/clock.md +++ b/docs/src/clock.md @@ -35,7 +35,7 @@ The recommended approach is to use `setFixedTime` to set the time to a specific ::: :::warning -If you call `install` at any point in your test, the call _MUST_ occur before any other clock related calls (see note above for list). For example, you cannot call `setInterval`, followed by `install`, then `clearInterval`, as `install` overrides the native definition of the clock functions. +If you call `install` at any point in your test, the call _MUST_ occur before any other clock related calls (see note above for list). Calling these methods out of order will result in undefined behavior. For example, you cannot call `setInterval`, followed by `install`, then `clearInterval`, as `install` overrides the native definition of the clock functions. ::: ## Test with predefined time