Skip to content

bun: test coverage is thin #23889

Description

@isaacs
  • 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

  1. linear-code commented on Sep 2, 2026

    @linear-code
  2. added
    javascriptPull requests that update javascript code
    on Sep 2, 2026
  3. added a commit that references this issue on Sep 29, 2026
    343ca07
  4. github-actions commented on Oct 1, 2026

    @github-actions
    Contributor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BunTestsjavascriptPull requests that update javascript code

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions