enzymejs/enzyme

Render throttling

Open

#1418 opened on Dec 7, 2017

View on GitHub
 (6 comments) (0 reactions) (0 assignees)JavaScript (19,979 stars) (2,016 forks)batch import
help wanted

Description

Nowadays more and more people start using enzyme for integration tests, abandoning the lands of Webdriver. Enzyme is a great thing for unit tests, but not the perfect for the integration ones.

And that's why: React throttles setState, applying the changes on next tick. React doing the same for render materializing VDom not instantly. As result, if on componentWillMount you will dispatch redux event, you will get the old store during the render.

Current synchronius model is ideal for units tests, but is it possible to make enzyme behaviour more React-ish? Add some debounce to make it more async, and more real?

Contributor guide

Tech stack
javascriptreact
Domain
testing
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
ReactenzymeJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate React's setState batching and asynchronous rendering behavior. Examine enzyme's current synchronous rendering implementation in the source code (likely in packages/enzyme/src/). Look for any existing discussions or PRs addressing async behavior. Consider how to introduce a debounce or async mode without breaking existing unit tests. The issue comments may contain hints about feasibility.