From 90748b11988798077618fe841e0e13b5fc7061a0 Mon Sep 17 00:00:00 2001
From: Stephen Toub <stoub@microsoft.com>
Date: Tue, 15 Apr 2025 19:00:43 -0400
Subject: [PATCH] Delete faulty assert (#313)

We need better coverage of Subscribe/Unsubscribe separately, but for now this assert is bad.
---
 tests/ModelContextProtocol.Tests/ClientIntegrationTests.cs | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/tests/ModelContextProtocol.Tests/ClientIntegrationTests.cs b/tests/ModelContextProtocol.Tests/ClientIntegrationTests.cs
index d6944df..dc01c92 100644
--- a/tests/ModelContextProtocol.Tests/ClientIntegrationTests.cs
+++ b/tests/ModelContextProtocol.Tests/ClientIntegrationTests.cs
@@ -307,11 +307,6 @@ public partial class ClientIntegrationTests : LoggedTest, IClassFixture<ClientIn
 
         // unsubscribe
         await client.UnsubscribeFromResourceAsync("test://static/resource/1", TestContext.Current.CancellationToken);
-        receivedNotification = new();
-
-        // wait a bit to validate we don't receive another. this is best effort only;
-        // false negatives are possible.
-        await Assert.ThrowsAsync<TimeoutException>(() => receivedNotification.Task.WaitAsync(TimeSpan.FromSeconds(1), TestContext.Current.CancellationToken));
     }
 
     [Theory]