Merge branch 'main' into wip/mobile

1 files changed, 45 insertions, 0 deletions

diff --git a/src/event/routes/test/setup.rs b/src/event/routes/test/setup.rs
new file mode 100644
index 0000000..007b03d
--- /dev/null
+++ b/src/event/routes/test/setup.rs
@@ -0,0 +1,45 @@
+use axum::extract::State;
+use axum_extra::extract::Query;
+use futures::{future, stream::StreamExt as _};
+
+use crate::{
+    event::routes::get,
+    test::fixtures::{self, future::Expect as _},
+};
+
+// There's no test for this in subscribe-then-setup order because creating an
+// identity to subscribe with also completes initial setup, preventing the
+// test from running. That is also a can't-happen scenario in reality.
+#[tokio::test]
+async fn previously_completed() {
+    // Set up the environment
+
+    let app = fixtures::scratch_app().await;
+
+    // Complete initial setup
+
+    let (name, password) = fixtures::login::propose();
+    let (owner, _) = app
+        .setup()
+        .initial(&name, &password, &fixtures::now())
+        .await
+        .expect("initial setup in an empty app succeeds");
+
+    // Subscribe to events
+
+    let subscriber = fixtures::identity::create(&app, &fixtures::now()).await;
+    let get::Response(events) =
+        get::handler(State(app.clone()), subscriber, None, Query::default())
+            .await
+            .expect("subscribe never fails");
+
+    // Expect a login created event
+
+    let _ = events
+        .filter_map(fixtures::event::login)
+        .filter_map(fixtures::event::login::created)
+        .filter(|event| future::ready(event.login == owner))
+        .next()
+        .expect_some("a login created event is sent")
+        .await;
+}