Filip/playwright
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

Add undefined behavior clarity

Browse source
This commit is contained in:
Adam Gastineau 2024-12-06 11:27:32 -08:00
parent b48e886674
commit 2bfa6a5684
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/src/clock.md
View file

@ -35,7 +35,7 @@ The recommended approach is to use `setFixedTime` to set the time to a specific
::: :::
:::warning :::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 ## Test with predefined time