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
Virtual DOM has a lot of potential in testing. But actually only ShallowRenderer uses it in 100%, which is great. But it's only usable for unit testing. Library like Enzyme are great in deep rendering w/o real DOM, which is huge performance boost in case of functional (or/and integration) testing without real browser. But it uses DOM mock, which is called jsdom.
In my opinion it is totally unnecessary, because VirtualDOM rendered output is totally usable for testing (which ShallowRenderer proves).
So I made little hacky but fully working patch to ShallowRenderer, which allows to render children also (PR here).
So my propose is introduce something like DeepRenderer in test utils. I can modify my patch.
Is it worth to skip jsdom? Will it be noticable perf boost? How to name that renderer? How the API should look like?
The text was updated successfully, but these errors were encountered:
I think this has been added in #6944, and while the exact API is subject to change, you might want to track what happens to it in a few weeks! I’ll close because it already exists and will be out soon.
Virtual DOM has a lot of potential in testing. But actually only ShallowRenderer uses it in 100%, which is great. But it's only usable for unit testing. Library like Enzyme are great in deep rendering w/o real DOM, which is huge performance boost in case of functional (or/and integration) testing without real browser. But it uses DOM mock, which is called jsdom.
In my opinion it is totally unnecessary, because VirtualDOM rendered output is totally usable for testing (which ShallowRenderer proves).
So I made little hacky but fully working patch to ShallowRenderer, which allows to render children also (PR here).
So my propose is introduce something like
DeepRenderer
in test utils. I can modify my patch.Is it worth to skip jsdom? Will it be noticable perf boost? How to name that renderer? How the API should look like?
The text was updated successfully, but these errors were encountered: