Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for domino #26

Closed
cscott opened this issue May 16, 2014 · 5 comments
Closed

Support for domino #26

cscott opened this issue May 16, 2014 · 5 comments

Comments

@cscott
Copy link

cscott commented May 16, 2014

jsdom is painfully slow and has native dependencies. It would be great if jest would support using the domino DOM implementation instead: https://github.com/fgnass/domino

@jeffmo
Copy link
Contributor

jeffmo commented May 16, 2014

Having something faster than jsdom does sound intriguing -- this is worth looking into (I hadn't seen it before).

Even if we were to switch though, we'd still want to be able to run tests in Contextify contexts/Realms (so we can quickly and cheaply dispose/construct new ones) -- so I think a native dependency there would continue to be necessary for the foreseeable future

@KyleAMathews
Copy link
Contributor

Perhaps use Karma?

Agree about switching off JSDOM. Test runs wildly vary in time from 2-20 seconds even for very simple 1 test files.

@ghost
Copy link

ghost commented Aug 4, 2015

Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.

@cpojer
Copy link
Member

cpojer commented Feb 23, 2016

This should be possible by providing the testEnvironment_EXPERIMENTAL config option. I'm going to close this because it isn't on Jest's roadmap but I will most certainly welcome contributions to Jest around this. See the JSDOMEnvironment and NodeEnvironment for examples.

@cpojer cpojer closed this as completed Feb 23, 2016
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 14, 2021
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

4 participants