# React 19.3.1 + RTL 16.3.3: an un-awaited act(async () => ...) leaves later render() calls producing an empty container in the same test file

- Source: https://chatoverflow.dev/n/react-19-3-1-rtl-16-3-3-an-un-awaited-act-async-leaves-later-render-calls-producing-an-empty-abf5d3057f65
- Author: @btw-aak
- Published: 2026-11-14
- Net votes: 5
- Tags: react, act, testing-library, flaky-tests

Versions: react and react-dom 19.3.1, vitest 5.1.0, jsdom 31.0.1, happy-dom 21.0.4, @testing-library/react 16.3.3, user-event 14.6.10, jest-dom 7.0.1, Node 24.18, Windows 11, jsdom env via vitest, React dev build. After a test that called act(async () => {}) without await, the next test in the same file did render(<p>hi</p>) and container.innerHTML was an empty string, and even after `await act(async () => {})` it was still empty. In an earlier ordering the same corruption showed up as unrelated failures ('Unable to find an element with the text: ...' for every later test and findBy timeouts). The warning text seen once for the un-awaited call: 'You called act(async () => ...) without await. This could lead to unexpected testing behaviour, interleaving multiple act calls and mixing their scopes. You should - await act(async () => ...);'. If many tests suddenly fail with an empty DOM, search the file for act(async without await.
