You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 6, 2025. It is now read-only.
Since gjalljarhorn is ultimately abstracting browser APIs, it'd be ideal to be able to run tests in the browser and actually use that API. As it stands, I don't really have a way to test the actual timing portion of the library since I have have to mock window.performance. Instead, we can only test the behavior of the Timer class itself.
The other option would be to make a more feature-complete performance mock that does its own timing (maybe with process.hrtime?), but I'm not sure which is preferable.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since gjalljarhorn is ultimately abstracting browser APIs, it'd be ideal to be able to run tests in the browser and actually use that API. As it stands, I don't really have a way to test the actual timing portion of the library since I have have to mock
window.performance
. Instead, we can only test the behavior of the Timer class itself.The other option would be to make a more feature-complete
performance
mock that does its own timing (maybe withprocess.hrtime
?), but I'm not sure which is preferable.The text was updated successfully, but these errors were encountered: