You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bun test reports 50 tests across 5 files. Cloudflare has 929, hono 241.
No tests at all for plugin.ts, client.ts, integrations/fetch.ts.
dev-packages/bun-integration-tests has 5 suites: basic, fetch, hono-sdk, orchestrion-mysql, orchestrion-postgres. Deno has 24.
Bun tests run under bun test, not vitest, so yarn test at the repo root does not run them. Easy to forget locally.
Work item. Pick the three highest-value additions: plugin.ts (the only instrumentation path that actually works on Bun today), streaming responses once B3 lands, and one more real orchestrion integration suite that goes through Bun.build (redis or express).
**Prior art **(related history only). #18635 (open) "Expand canary test coverage across all framework SDKs" is the nearest umbrella. No issue covers the Bun unit or integration test gap specifically.
Activity
linear-code commentedon Sep 2, 2026
JS-3515
test(bun, deno): Run shared Node integration suites on Bun and Deno (#…
test(bun): Run the Bun-only suites with the shared Node runner (#24668)
test(bun): Run all Node integration suites on Bun (#24610)
fix(bun): Keep diagnostics channel subscriptions alive (#24632)
test(bun): Run the auto-instrumentation suites with bundled scenarios (…
github-actions commentedon Oct 1, 2026
A PR closing this issue has just been released 🚀
This issue was referenced by PR #24612, which was included in the 11.2.0 release.