Tests for purged channels and messages.

This required a re-think of the `.immediately()` combinator, to generalize it to cases where a message is _not_ expected. That (more or less immediately) suggested some mixed combinators, particularly for stream futures (futures of `Option<T>`).

1 files changed, 3 insertions, 4 deletions

diff --git a/src/event/routes/test/setup.rs b/src/event/routes/test/setup.rs
index a54b65b..007b03d 100644
--- a/src/event/routes/test/setup.rs
+++ b/src/event/routes/test/setup.rs
@@ -4,7 +4,7 @@ use futures::{future, stream::StreamExt as _};
 
 use crate::{
     event::routes::get,
-    test::fixtures::{self, future::Immediately as _},
+    test::fixtures::{self, future::Expect as _},
 };
 
 // There's no test for this in subscribe-then-setup order because creating an
@@ -40,7 +40,6 @@ async fn previously_completed() {
         .filter_map(fixtures::event::login::created)
         .filter(|event| future::ready(event.login == owner))
         .next()
-        .immediately()
-        .await
-        .expect("a login created event is sent");
+        .expect_some("a login created event is sent")
+        .await;
 }