pytest-sentry

pytest-sentry copied to clipboard

pytest-sentry does not set its own hub as the current one. that leads to the unfortunate situation that all test code will create spans, but those spans go to the application's SDK setup which is probably just disabled.

we should find a way to capture spans in pytest-sentry without capturing transactions emitted by the application, or worse, capturing the app errors.

right now 99% of value brought by pytest-sentry is just triaging slow tests, but with operations breakdown this may change drastically