From 4526192257bee8f94aef844560f80a479e9a2576 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Fri, 31 Jul 2026 10:25:12 +0000
Subject: [PATCH 1/2] Initial plan


From ce32b4e24039dd6d9e7387ea3136d1e42cf58643 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Fri, 31 Jul 2026 10:33:25 +0000
Subject: [PATCH 2/2] fix: increase timeout for MongoDB cluster cleanup in
 integration test

The `after all` hook in the `With a MongoDB Cluster` suite was timing
out because `mochaTestServer`'s `after` hook (which calls
`cluster.close()` to stop the MongoDB server and clean up data files)
was inheriting the suite's 30-second timeout. Shutting down a MongoDB
server process and removing its data files can take longer than 30
seconds in CI environments.

Fix:
- Increase the suite timeout from 30s to 120s so that
  `mochaTestServer`'s `after` hook has enough time to complete cleanup
- Add an explicit `this.timeout(60_000)` to the test's own `after`
  hook for clarity
---
 .../test/integration/generate-and-validate.test.ts             | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/packages/mongodb-schema/test/integration/generate-and-validate.test.ts b/packages/mongodb-schema/test/integration/generate-and-validate.test.ts
index f2b8ea990..42abdb69b 100644
--- a/packages/mongodb-schema/test/integration/generate-and-validate.test.ts
+++ b/packages/mongodb-schema/test/integration/generate-and-validate.test.ts
@@ -54,7 +54,7 @@ describe('Documents -> Generate schema -> Validate Documents against the schema'
 });
 
 describe('With a MongoDB Cluster', function () {
-  this.timeout(30_000);
+  this.timeout(120_000);
 
   let client: MongoClient;
   let db: Db;
@@ -69,6 +69,7 @@ describe('With a MongoDB Cluster', function () {
   });
 
   after(async function () {
+    this.timeout(60_000);
     await client?.close();
   });