CoverBot: Covered core analytics and ESM loader utilities

[tusk-dev]

This PR contains 15 unit tests across 2 test files.

CoverBot config: Core Files

File patterns: src/core/**

Why these files?

analyticsUtils.ts had 19.4% line coverage (lowest in the report) and esmLoader.ts sat at 37.14%, both lacking test files entirely. CoverBot's tests brought both to 100% line coverage with 90% and 80.8% branch coverage respectively. These files contain branching logic critical to SDK initialization and signaling, and their low coverage represented the clearest gaps among testable core utilities. The test suite covers 2 exported functions and 5 distinct branches across both files.

Reviewers

Tagged @sohankshirsagar — authored the sole commit to both analyticsUtils.ts and esmLoader.ts

Files tested

• src/core/analytics/analyticsUtils.ts
• src/core/esmLoader.ts

Avg +100% line coverage gain across 2 files

Source file	Line	Branch
src/core/analytics/analyticsUtils.ts	100% (+100%)	90% (+90%)
src/core/esmLoader.ts	100% (+100%)	81% (+81%)

Coverage is calculated by running tests directly associated with each source file, learn more here.

---

View test details on Tusk ↗

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit a0709f5. Configure here.}

[cubic-dev-ai]

2 issues found across 3 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/core/esmLoader.test.ts">

<violation number="1" location="src/core/esmLoader.test.ts:24">
P2: These tests mutate shared state (`_esmLoaderDeps`, `globalThis.__tuskDriftEsmLoaderRegistered`, `require('import-in-the-middle')` exports) but use `test()` instead of `test.serial()`. AVA runs tests concurrently by default within a file, so one test's mock can bleed into another, causing flaky failures. All tests in this file that touch shared mutable state should use `test.serial` instead.</violation>
</file>

<file name="src/core/analytics/analyticsUtils.test.ts">

<violation number="1" location="src/core/analytics/analyticsUtils.test.ts:26">
P2: These tests mutate shared state (`TuskDriftCore.getInstance`) via `withMockedInstance` but use `test()` instead of `test.serial()`. AVA runs tests concurrently by default, so concurrent tests could overwrite each other's mock of `getInstance`, causing flaky failures. Use `test.serial` for all tests that touch shared mutable state.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review, or fix all with cubic.}