getsentry / getsentry/sentry-javascript

browser-integration-tests: drop static pins from non-tracing suites

Abierto
#24,145 1 comentario 0 reacciones 1 asignado Reclamado por @msonnb Ver en GitHub
javascript Task
Lenguaje dominante
TypeScript
Estrellas
8.7k
Forks
1.8k
Merge medio
1 d 17 h
PR fusionados (30 d)
523

Descripción

Follow the porting recipe in the parent issue.

Largest group by file count and the smallest by effort. Around 226 pinned `init.js` files never assert on a transaction envelope, so the pin just needs to go.

## Suites (pin removal only)

* `replay/*` (78 files, the single biggest block)
* `feedback/*`, `sessions/*`, `errors/*`, `stacktraces/*`, `transport/*`, `wasm/*`, `old-sdk-interop/*`, `manual-client/*`, `ipv6`
* `public-api/*` except the span surface dirs owned by the trace semantics sub-issue
* `integrations/*` except `httpclient`, which the trace semantics sub-issue owns

## Watch-outs

* `replay/dsc` and `public-api/dataCollection` do assert on the trace context, so they need a rewrite rather than a pin removal.
* `profiling/traceLifecycleMode_multiple-chunks` and `traceLifecycleMode_overlapping-spans` intentionally test the static lifecycle. Leave their pins in place.
* `integrations/cultureContext-streamed` and `integrations/httpContext-streamed` are twins. Fold them back into their static originals.

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.