firebase / firebase-js-sdk / 37522112260

62%

master: 0%

push

github

test(compat): migrate installations, analytics, functions, and app compat to Vitest (#10408)

* test(installations-compat): migrate installations-compat to Vitest

Migrate @firebase/installations-compat unit tests from legacy Karma/Mocha/Chai/Sinon to native Vitest with Playwright browser runner.
- Replace karma.conf.js with vitest.config.mjs filtering to browser runner
- Standardize package.json test scripts for browser-only SDK
- Replace Sinon stubs with vi.mock({ spy: true }) and vi.spyOn
- Replace Chai assertions with native Vitest expect matchers
- Add global mock cleanup in test/setup.ts and ambient vitest-globals.d.ts

Performance & CI Impact:
• Test Count: 4 passed (100% parity, 0 regressions)
• Before (Karma): 3.23s
• After (Vitest Browser): 0.54s
• Memory / Isolation: pool: 'forks', maxForks: 2, 0MB display buffer

* test(installations-compat): address review comments on mock returns and teardown order

* test(analytics-compat): migrate analytics-compat to Vitest

Migrate @firebase/analytics-compat unit tests from legacy Karma/Mocha/Chai/Sinon to native Vitest with Playwright browser runner.
- Replace karma.conf.js with vitest.config.mjs filtering to browser runner
- Standardize package.json test scripts for browser-only SDK
- Replace Sinon stubs with vi.mock({ spy: true }) and vi.spyOn
- Replace Chai assertions with native Vitest expect matchers
- Add global mock cleanup in test/setup.ts and ambient vitest-globals.d.ts

Performance & CI Impact:
• Test Count: 10 passed (100% parity, 0 regressions)
• Before (Karma): 2.96s
• After (Vitest Browser): 0.54s
• Memory / Isolation: pool: 'forks', maxForks: 2, 0MB display buffer

* test(functions-compat): migrate functions-compat to Vitest

Migrate @firebase/functions-compat unit tests from legacy Karma/Mocha/Chai/Sinon to native Vitest with Playwright browser and Node runners.
- Replace karma.conf.js with vitest.config.mjs supporting both node and browser runners
- Update package.json scripts to use... (continued)

3399 of 6033 branches covered (56.34%)

Branch coverage included in aggregate %.

9857 of 13518 relevant lines covered (72.92%)

441.1 hits per line