[Testing] User-facing screens and Salesforce integration layer have 0% coverage #40

Summary

The unit suite is green (37 suites / 456 tests), but coverage is concentrated in pure utilities. The production UI and integration boundaries that users rely on are effectively untested.

Reproduction

npm run test:coverage -- --runInBand

Current result

• Overall: 12.55% statements, 10.05% branches, 6.02% functions, 12.93% lines.
• ui/app/AppRoot.tsx: 0%.
• All files under ui/screens: 0%.
• All files under ui/components: 0%.
• ui/api/sf.ts: 0%.
• Salesforce auth and Bulk API: 0%.
• Background/offscreen entry points: 0%.
• Popup and panel roots: 0%.

This gap allowed reproducible navigation, Compare, Schedule, Export, and accessibility defects to coexist with 456 passing tests.

Recommended minimum matrix

• AppRoot route/navigation tests, including every Help/onboarding target.
• Core smoke flows: query→results→four formats; import file→mapping→dry run; Convert round trips; local Compare orientation/key selection; schedule prefill/save/run/retention.
• Popup and in-page panel smoke tests.
• Salesforce message contract tests for success, auth expiry, timeout, partial failure, and MV3 worker restart.
• Migration CRUD/workspace/validation/report/id-map flows.
• Automated accessibility scan on representative screens and modals.

Acceptance criteria

• CI publishes coverage and enforces agreed thresholds for changed code.
• At least one interaction test covers every navigable screen.
• Headline export/import/convert/compare/schedule flows have end-to-end-style tests with mocked Chrome/Salesforce boundaries.
• Regression tests are added for the defects found in this audit.

Environment

• Commit: 01a5279 (main)
• WaveLink: 0.2.0
• Windows 11 Home
• Chrome 146.0.7680.216 (T3 Code preview)
• Node 24.19.0 / npm 11.17.0