Skip to content
This repository has been archived by the owner on Jan 6, 2025. It is now read-only.

Use actual browser tests instead of Jest #1

Open
cafreeman opened this issue Jun 30, 2018 · 0 comments
Open

Use actual browser tests instead of Jest #1

cafreeman opened this issue Jun 30, 2018 · 0 comments

Comments

@cafreeman
Copy link
Contributor

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant