getsentry / getsentry/sentry-javascript
browser-integration-tests: drop static pins from non-tracing suites
- Dominant language
- TypeScript
- Stars
- 8.7k
- Forks
- 1.8k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 515
Description
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.
Contributor guide
Assessment
This issue has not been assessed yet.