Use WXT's testing harness, don't reinvent the wheel.

Author: ntwigg

browser-extension/tests/setup.ts

@@ -1,38 +1 @@
 import '@testing-library/jest-dom/vitest'
-import { vi } from 'vitest'
-
-// Mock browser APIs
-interface GlobalWithBrowser {
-  browser: {
-    runtime: {
-      sendMessage: ReturnType<typeof vi.fn>
-      onMessage: {
-        addListener: ReturnType<typeof vi.fn>
-      }
-    }
-  }
-  chrome: GlobalWithBrowser['browser']
-}
-
-const globalWithBrowser = global as unknown as GlobalWithBrowser
-
-globalWithBrowser.browser = {
-  runtime: {
-    onMessage: {
-      addListener: vi.fn(),
-    },
-    sendMessage: vi.fn(),
-  },
-}
-
-globalWithBrowser.chrome = globalWithBrowser.browser
-
-// Mock console methods to reduce noise in tests
-global.console = {
-  ...console,
-  debug: vi.fn(),
-  error: vi.fn(),
-  info: vi.fn(),
-  log: vi.fn(),
-  warn: vi.fn(),
-}

browser-extension/vitest.config.ts

@@ -1,14 +1,8 @@
-import path from 'node:path'
 import { defineConfig } from 'vitest/config'
+import { WxtVitest } from 'wxt/testing'
 
 export default defineConfig({
-  resolve: {
-    alias: {
-      '@': path.resolve(__dirname, './entrypoints'),
-      '@content': path.resolve(__dirname, './entrypoints/content'),
-      '@utils': path.resolve(__dirname, './entrypoints/content/utils'),
-    },
-  },
+  plugins: [WxtVitest()],
   test: {
     coverage: {
       exclude: [