Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

node-integration-tests: port AI and gen_ai suites to span streaming

Open
#24,138 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
54/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
node.js, typescript
Domain
testing-qa

Research direction

Start with the parent issue's porting recipe, then inspect the listed node integration suites and their span-streaming variants. Pay particular attention to deep gen_ai attributes on child spans, the { value, type } shape, and collecting attributes across envelopes. Fold the specified Vercel AI twins into their matching suites and remove the listed suffix where applicable; the suites should cover the same streaming behavior afterward.

Written by the indexing model from the issue text.

Description

javascript Task

Follow the porting recipe in the parent issue.

These suites assert on deep gen_ai attribute sets on child spans, so the { value, type } attribute shape and the collect-across-envelopes rule matter more here than anywhere else.

Suites

  • tracing/openai, tracing/openai/openai-tool-calls, tracing/openai/v6, tracing/openai/v7
  • tracing/anthropic
  • tracing/google-genai, tracing/google-genai-v2
  • tracing/vercelai, tracing/vercelai/v5, tracing/vercelai/v6_v7
  • tracing/langchain, tracing/langchain/v1
  • tracing/langgraph
  • aws-serverless/bedrock

Twins to fold back

  • tracing/vercelai/span-streaming-v4 and tracing/vercelai/span-streaming-v6 into the matching vercelai suites
  • tracing/mcp-server-streamed has no static original, so just drop the suffix
Dominant language
TypeScript
Stars
8.7k
Forks
1.9k
Avg merge
1d 18h
Merged PRs (30d)
562

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/sentry-javascript

All issues in getsentry/sentry-javascript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.