In streaming mode, record_sql_queries calls sentry_sdk.start_span() which delegates to Scope.start_span(). When streaming is enabled, Scope.start_span() returns NoOpSpan() (scope.py:1214). The test then tries to set _start_timestamp and _timestamp (with underscore prefix) on this NoOpSpan, but NoOpSpan inherits from Span which only has start_timestamp and timestamp (without underscore) in __slots__. This causes an AttributeError because NoOpSpan doesn't allow arbitrary attribute assignment.

Also found at:

• tests/integrations/sqlalchemy/test_sqlalchemy.py:1212-1213
• tests/integrations/sqlalchemy/test_sqlalchemy.py:293

When root_span=None (streaming mode), the code attempts to find a root span by looking for a span without parent_span_id. If no such span exists in the list, root_span remains None, and line 509 will raise a runtime error when calling render_span(root_span). This could cause cryptic test failures.

Also found at:

• tests/conftest.py:485-487

The isinstance(span, StreamedSpan) check on line 101 will never be true. The span comes from record_sql_queries() which internally calls sentry_sdk.start_span(). When span streaming is enabled, sentry_sdk.start_span() returns NoOpSpan (not StreamedSpan). When streaming is disabled, it returns Span. Neither is a StreamedSpan, making this error handling code unreachable.

Also found at:

• sentry_sdk/integrations/sqlalchemy.py:142-177

The span streaming branch of test_transactions only asserts SPANDATA.SERVER_PORT not in span["attributes"], while the non-streaming branch checks both SPANDATA.SERVER_ADDRESS not in span["data"] and SPANDATA.SERVER_PORT not in span["data"]. This asymmetry means the streaming path does not verify SERVER_ADDRESS is absent, reducing test coverage for the span streaming feature.

Also found at:

• tests/integrations/sqlalchemy/test_sqlalchemy.py:293

The span streaming branch (lines 811-813) only checks for CODE_LINE_NUMBER, CODE_FILE_PATH, and CODE_FUNCTION_NAME attributes, but omits the CODE_NAMESPACE check that exists in the non-streaming branch (lines 864-867, 871). This asymmetry in test coverage could allow a regression where span streaming mode fails to include namespace information.

In test_no_query_source_if_duration_too_short, inside the else: branch (line 962), the fake_record_sql_queries class contains an if span_streaming: check (lines 989-994). Since this code is inside the else: # span_streaming is False branch, the if span_streaming: block (lines 989-991) is unreachable dead code. While the test still works correctly because the else: path is taken, this appears to be an artifact of copy-paste during refactoring that should be cleaned up.