FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

node-integration-tests: port database, cache and messaging suites to span streaming · Issue #24137 · getsentry/sentry-javascript · GitHub

Repository navigation

node-integration-tests: port database, cache and messaging suites to span streaming #24137

Description

Follow the porting recipe in the parent issue.

Most of these run under docker compose, so plan for a slow feedback loop. db span names became low cardinality and redis spans now start as cache spans, so nearly every name and op assertion changes.

Suites

  • Postgres: tracing/postgres, tracing/postgresjs
  • MySQL: tracing/mysql, tracing/mysql2, tracing/mysql2-tracing-channel
  • Mongo: tracing/mongodb, tracing/mongodb-v4 to -v7, tracing/mongoose, tracing/mongoose-v5 to -v9, tracing/mongoose-tracing-channel
  • Prisma: tracing/prisma-orm-v5, -v6, -v7
  • Other: tracing/knex/mysql2, tracing/knex/pg, tracing/tedious, tracing/genericPool, tracing/genericPool-v2, tracing/dataloader
  • Cache: tracing/redis, tracing/redis-cache, tracing/redis-dc, tracing/ioredis-dc
  • Messaging: tracing/kafkajs, tracing/amqplib

Twins to fold back

  • tracing/postgres-streamed into tracing/postgres
  • tracing/postgresjs-streamed into tracing/postgresjs

Env-gated suites

13 of these use traceLifecycle: process.env.STREAMED === 'true' ? 'stream' : 'static' (all the mongo, mongoose, redis and ioredis suites plus tracing/mysql and tracing/dataloader). Drop the switch and keep 'stream'.

Metadata

Metadata

Assignees

Labels

TaskjavascriptPull requests that update javascript code

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


    Back | FazBrowse Home | New Git URL