Multiple test cases create SentryAttachment(default, default, default, "test.txt") where the intent appears to be setting the fileName to "test.txt". However, the constructor signature is (AttachmentType type, IAttachmentContent content, string fileName, string? contentType), so "test.txt" is being assigned to contentType while fileName is null. This creates malformed attachment objects that may not accurately test the scope sync behavior if the observer implementation relies on the attachment filename.