use persistentContext for setup also

interledger · Sep 12, 2024 · 263586d · 263586d
1 parent c0f1f49
commit 263586d
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 2 deletions.
diff --git a/tests/e2e/auth.setup.ts b/tests/e2e/auth.setup.ts
@@ -1,4 +1,4 @@
-import { test as setup, expect } from '@playwright/test';
+import { test as setup, expect } from './fixtures/base';
 import { authFile } from './fixtures/helpers';
 
 // Authenticate with wallet once in "setup" so we don't have to do it over and

diff --git a/tests/e2e/fixtures/helpers.ts b/tests/e2e/fixtures/helpers.ts
@@ -171,7 +171,13 @@ export async function loadContext({ browserName, channel }: BrowserInfo) {
 
   // Note that loading this directly via config -> use({ storageState }) doesn't
   // work correctly with our browser context. So, we addCookies manually.
-  const { cookies } = await readFile(authFile, 'utf8').then(JSON.parse);
+  const { cookies } = await readFile(authFile, 'utf8')
+    .then(JSON.parse)
+    .catch(() => {
+      // eslint-disable-next-line no-console
+      console.log('loadContext: authFile does not exist');
+      return { cookies: [] };
+    });
   await context.addCookies(cookies);
 
   return context;