In order to support the new threlte/test-renderer, exposing the low-level rendering and cleanup core of @testing-library/svelte will allow the two projects to share a bunch of common logic, and provide a better experience for users writing tests for Svelte applications with Threlte.
This PR adds the proposed documentation for this core as a little form of README-driven-development. I've taken a look at the Threlte test-renderer source code, and I think these methods would allow a lot of good functionality re-use while remaining flexible to both projects' needs
mcous
commented
1 day ago
In order to support the new threlte/test-renderer, exposing the low-level rendering and cleanup core of
@testing-library/sveltewill allow the two projects to share a bunch of common logic, and provide a better experience for users writing tests for Svelte applications with Threlte.This PR adds the proposed documentation for this core as a little form of README-driven-development. I've taken a look at the Threlte test-renderer source code, and I think these methods would allow a lot of good functionality re-use while remaining flexible to both projects' needs
Rendered output