Hydration mismatch during rapid state updates in newSpec

When testing Stencil components using the @stencil/core testing library, maintaining consistency between the initial server-rendered state and the client-side DOM is critical. While the newSpec utility facilitates mounting components and simulating lifecycle methods, certain state-driven updates can trigger hydration mismatch warnings.

The issue arises specifically when rapid-fire state re-renders occur immediately after the component mounts. This creates a potential race condition where the test assertion may execute before the virtual DOM has fully synchronized with the asynchronous state, leading to inconsistent test results that do not reflect production-like behavior.

• How does the Stencil runtime handle the priority of asynchronous CSS transitions during these rapid render cycles?
• Is there a configuration option to ensure the hydration process completes fully before newSpec assertions are evaluated?