Agreed, tests run in both node/browsers in realtime. See popper: https://github.com/pemrouz/popper .
-
-
Replying to @pemrouz @notwaldorf and
Most people don't do this though, see shallow rendering. Only being able to run in DOM is just another unnecessary hurdle.
1 reply 0 retweets 0 likes -
Replying to @pemrouz @notwaldorf and
If the element is meant to run in the DOM, testing in actual DOM seems to be the only safe thing to do.
1 reply 0 retweets 4 likes -
Replying to @justinfagnani @pemrouz and
Unit testing React components in non-DOM env is a great way to test logic fast. End-to-end browser tests also important, but perf matters
1 reply 0 retweets 1 like -
Replying to @dfabu @justinfagnani and
Uhhhhhhhh...how slow is headless chrome on your box, exactly?
1 reply 0 retweets 0 likes -
-
Replying to @dfabu @slightlylate and
There's https://github.com/tmpvar/jsdom - you just need to be aware you're essentially testing in a different agent.
2 replies 0 retweets 1 like -
Replying to @jaffathecake @slightlylate and
We got a big perf boost going from PhantomJS to jsdom, and another big boost going to virtual DOM. jsdom tries to simulate a whole browser.
1 reply 0 retweets 0 likes -
Replying to @dfabu @jaffathecake and
Headless Chrome is a perf boost. - phantom2: engine 2yrs+ old, Roughly Safari 8. - jsdom/node8 - V8 v5.8 - Headless Chrome: Blink, V8 v5.9.
2 replies 0 retweets 4 likes -
Replying to @ebidel @jaffathecake and
That makes sense, but virtual DOM is unbeatable for testing performance
1 reply 0 retweets 1 like
There's always a perf win available from reducing fidelity & correctness 
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.