Revert the changes and capture traces!

Author: timfish

dev-packages/browser-integration-tests/playwright.config.ts

@@ -7,11 +7,11 @@ const config: PlaywrightTestConfig = {
   fullyParallel: true,
   // Use 3 workers on CI, else use defaults (based on available CPU cores)
   // Note that 3 is a random number selected to work well with our CI setup
-  workers: process.env.CI ? 3 : undefined,
+  workers: process.env.GITHUB_ACTIONS ? 3 : undefined,
   testMatch: /test.ts/,
 
   use: {
-    trace: process.env.CI ? 'retry-with-trace' : 'off',
+    trace: process.env.GITHUB_ACTIONS ? 'retry-with-trace' : 'off',
   },
 
   projects: [

dev-packages/browser-integration-tests/suites/replay/captureReplayOffline/init.js

@@ -12,6 +12,6 @@ Sentry.init({
   sampleRate: 0,
   replaysSessionSampleRate: 1.0,
   replaysOnErrorSampleRate: 0.0,
-  // transport: Sentry.makeBrowserOfflineTransport(),
+  transport: Sentry.makeBrowserOfflineTransport(),
   integrations: [window.Replay],
 });

dev-packages/browser-integration-tests/suites/replay/captureReplayOffline/test.ts

@@ -25,7 +25,7 @@ sentryTest('should capture replays offline', async ({ getLocalTestPath, page })
   // await context.setOffline(true);
 
   // Abort the first envelope request so the event gets queued
-  // await page.route(/ingest\.sentry\.io/, route => route.abort(), { times: 1 });
+  await page.route(/ingest\.sentry\.io/, route => route.abort('internetdisconnected'), { times: 1 });
 
   await page.goto(url);