# test\(web\): render browser tests through vitest-browser-react · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/273bef5e0df7fccffea42d3ee17e4ec021f2853a)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 273bef5e0df7fccffea42d3ee17e4ec021f2853a

Requested commit: 273bef5e0df7fccffea42d3ee17e4ec021f2853a

Commit: 273bef5e0df7fccffea42d3ee17e4ec021f2853a

Tree: 4df5bc63294808f005d697745861e4ef67878842

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
test(web): render browser tests through vitest-browser-react

Most of the web suite's console noise came from tests opting into React's act
environment for the whole test while driving the UI with real browser events,
plus components rendered without a router. Add a shared render helper built on
vitest-browser-react that only enables the act environment inside act(), wraps
the tree in a memory router, and re-renders in place per container. Migrate the
nine noisiest browser test files to it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

- [ce2815d665acb0dedc028c12109d3b7aebbcc134](https://git.cafe/pingdotgg/t3code/commit/ce2815d665acb0dedc028c12109d3b7aebbcc134?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/273bef5e0df7fccffea42d3ee17e4ec021f2853a?format=markdown)