test: Fix node-integration-test timeouts & cleanup (#13280)

This PR streamlines and fixes some timing/cleanup issues we had in
integration tests, which sometimes lead to issues.

One problem was introduced here:
#13253

This change lead to the server being shut down (because `done` is
called) before the HTTP requests are finished, leading to error logs.

Another problem was that in some cases we had leaking processes, where
we did not properly close servers we started - this was everywhere we
used `createTestServer`.

I also moved some code from the node-integration-tests package to the
remix package, that was only used there (and not properly
depended/imported on).

For future debugging, this was shown by running tests with
`--detectOpenHandles`.

Author: mydea

dev-packages/node-integration-tests/README.md

@@ -38,14 +38,6 @@ requests, and assertions. Test server, interceptors and assertions are all run o
 
 `utils/` contains helpers and Sentry-specific assertions that can be used in (`test.ts`).
 
-`TestEnv` class contains methods to create and execute requests on a test server instance. `TestEnv.init()` which starts
-a test server and returns a `TestEnv` instance must be called by each test. The test server is automatically shut down
-after each test, if a data collection helper method such as `getEnvelopeRequest` and `getAPIResponse` is used. Tests
-that do not use those helper methods will need to end the server manually.
-
-`TestEnv` instance has two public properties: `url` and `server`. The `url` property is the base URL for the server. The
-`http.Server` instance is used to finish the server eventually.
-
 Nock interceptors are internally used to capture envelope requests by `getEnvelopeRequest` and
 `getMultipleEnvelopeRequest` helpers. After capturing required requests, the interceptors are removed. Nock can manually
 be used inside the test cases to intercept requests but should be removed before the test ends, as not to cause

dev-packages/node-integration-tests/jest.setup.js

@@ -1,7 +1,7 @@
 const { cleanupChildProcesses } = require('./utils/runner');
 
-// Increases test timeout from 5s to 45s
-jest.setTimeout(45000);
+// Default timeout: 15s
+jest.setTimeout(15000);
 
 afterEach(() => {
   cleanupChildProcesses();

dev-packages/node-integration-tests/suites/express/multiple-init/server.ts

@@ -54,15 +54,19 @@ app.get('/test/error/:id', (req, res) => {
 
   setTimeout(() => {
     // We flush to ensure we are sending exceptions in a certain order
-    Sentry.flush(3000).then(
+    Sentry.flush(1000).then(
       () => {
+        // We send this so we can wait for this, to know the test is ended & server can be closed
+        if (id === '3') {
+          Sentry.captureException(new Error('Final exception was captured'));
+        }
         res.send({});
       },
       () => {
         res.send({});
       },
     );
-  }, 1000);
+  }, 1);
 });
 
 Sentry.setupExpressErrorHandler(app);

dev-packages/node-integration-tests/suites/express/multiple-init/test.ts

@@ -48,6 +48,17 @@ test('allows to call init multiple times', done => {
         },
       },
     })
+    .expect({
+      event: {
+        exception: {
+          values: [
+            {
+              value: 'Final exception was captured',
+            },
+          ],
+        },
+      },
+    })
     .start(done);
 
   runner

dev-packages/node-integration-tests/suites/public-api/LocalVariables/test.ts

@@ -3,6 +3,10 @@ import * as path from 'path';
 import { conditionalTest } from '../../../utils';
 import { cleanupChildProcesses, createRunner } from '../../../utils/runner';
 
+// This test takes some time because it connects the debugger etc.
+// So we increase the timeout here
+jest.setTimeout(45_000);
+
 const EXPECTED_LOCAL_VARIABLES_EVENT = {
   exception: {
     values: [

dev-packages/node-integration-tests/suites/tracing/connect/scenario.js

@@ -13,7 +13,7 @@ Sentry.init({
 const connect = require('connect');
 const http = require('http');
 
-const init = async () => {
+const run = async () => {
   const app = connect();
 
   app.use('/', function (req, res, next) {
@@ -34,4 +34,4 @@ const init = async () => {
   sendPortToRunner(port);
 };
 
-init();
+run();

dev-packages/node-integration-tests/suites/tracing/connect/test.ts

@@ -1,7 +1,5 @@
 import { cleanupChildProcesses, createRunner } from '../../../utils/runner';
 
-jest.setTimeout(20000);
-
 describe('connect auto-instrumentation', () => {
   afterAll(async () => {
     cleanupChildProcesses();

dev-packages/node-integration-tests/suites/tracing/hapi/scenario.js

@@ -13,7 +13,7 @@ const Boom = require('@hapi/boom');
 
 const port = 5999;
 
-const init = async () => {
+const run = async () => {
   const server = Hapi.server({
     host: 'localhost',
     port,
@@ -65,4 +65,4 @@ const init = async () => {
   sendPortToRunner(port);
 };
 
-init();
+run();

dev-packages/node-integration-tests/suites/tracing/hapi/test.ts

@@ -1,7 +1,5 @@
 import { cleanupChildProcesses, createRunner } from '../../../utils/runner';
 
-jest.setTimeout(20000);
-
 describe('hapi auto-instrumentation', () => {
   afterAll(async () => {
     cleanupChildProcesses();

dev-packages/node-integration-tests/suites/tracing/mongodb/test.ts

@@ -2,8 +2,6 @@ import { MongoMemoryServer } from 'mongodb-memory-server-global';
 
 import { cleanupChildProcesses, createRunner } from '../../../utils/runner';
 
-jest.setTimeout(20000);
-
 describe('MongoDB experimental Test', () => {
   let mongoServer: MongoMemoryServer;