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

browser-integration-tests: port trace semantics suites to span streaming

Open
#24,144 1 comment 0 reactions 1 assignee View on GitHub

@msonnb is already working on this.

Since Sep 7, 2026.

Assessment

This issue has not been assessed yet.

Description

javascript Task

Follow the porting recipe in the parent issue.

Trace lifetime, DSC, sampling and span linking. These assert on envelope headers and trace propagation rather than on instrumentation output, so they are the ones most likely to expose a real product bug rather than a test rewrite.

Suites

  • Trace lifetime: tracing/trace-lifetime/*, tracing/continueTrace/*, tracing/bindScopeToEmitter
  • Envelope headers and DSC: tracing/envelope-header, tracing/envelope-header-transaction-name, tracing/dsc-txn-name-update
  • Sampling: tracing/tracesSampler, tracing/stringSampleRate, tracing/no-parent-span-client-report
  • Span shaping: tracing/linking-addLink, tracing/linking-addLinks, tracing/linking-spanOptions, tracing/ignoreSpans, tracing/maxSpans, tracing/setSpanActive, tracing/microfrontend-span-attribution, tracing/browserTracingIntegrationShim
  • Public API span surface: public-api/startSpan, public-api/beforeSendTransaction
  • integrations/httpclient

Twins to fold back

tracing/trace-lifetime/pageload-streamed, navigation-streamed, startNewTrace-streamed, tracing/setSpanActive-streamed, tracing/linking-addLink-streamed, tracing/ignoreSpans-streamed, tracing/http-client-span-streamed, public-api/startSpan/streamed, public-api/beforeSendSpan-streamed.

Keep static trace lifecycle coverage

Pick one suite here to stay on the static pin as the guard, and name it in the PR. The profiling/traceLifecycleMode_* suites already cover the lifecycle switch itself.

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.