René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Feature]: Promote `testing` to Stable — settle the Testing-Library-parity surface","articleBody":"**Pre-flight checklist**\n- [x] I searched existing issues and did not find a duplicate request.\n- [x] I explained the problem or use case, not just the desired API.\n\n**Problem or use case**\n`testing` is **Beta** and its surface is one minor old: `screen`/`within`, `userEvent`, the `fireEvent.*` family, module mocks, and a11y helpers all landed in 1.14.0. It mirrors Testing Library APIs well (including Shadow-DOM-aware queries, which suit bQuery's Web Component model), but a test-utility API that just appeared cannot yet be relied on for teams' test suites, and the official runner integration story (beyond `bun:test`) is undocumented.\n\n**Proposed solution**\nFreeze the `testing` API for one cycle, document runner integration beyond `bun:test` (at minimum guidance for Vitest/Jest-style runners, since not every team uses Bun), and add coverage proving the query/`userEvent`/`fireEvent`/mock APIs behave consistently — especially the Shadow-DOM-aware queries against real components. Exit criteria: frozen surface, documented runner integrations, tested query/interaction APIs across light and shadow DOM.\n\n**Possible API or UX shape**\n```ts\nimport { render, screen, userEvent } from \"@bquery/bquery/testing\";\n\nrender(MyComponent, { props });\nawait userEvent.click(screen.getByRole(\"button\", { name: \"Save\" }));\n// Shadow-DOM-aware queries documented + tested; runner-agnostic guidance published\n```\n\n**Alternatives considered**\nPromoting now — premature for a 1.14-introduced surface. Supporting only `bun:test` officially — limits adoption to Bun users; documenting runner-agnostic usage costs little and broadens reach.\n\n**Relevant area**\n`testing`\n\n**Additional context**\nReuse the `a11y` audit API (#142) in the testing a11y helpers so assertions and runtime audits share one definition of \"accessible.\" Parity target: React Testing Library, Vue Test Utils, Svelte Testing Library.\n","author":{"url":"https://github.com/JosunLP","@type":"Person","name":"JosunLP"},"datePublished":"2026-06-26T21:25:53.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/147/bQuery/issues/147"}