chore(tests): remove orphaned scanner-era test suite #42
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/remove-stale-scanner-tests"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to the library rebuild + Immich reapply. The rebuild replaced the scanner app (root
lib//app/layout, Vitest + Playwright + Testing Library) with the current library app (src/layout,node:test) but left the wholetests/tree behind.Every
tests/**file imports deleted root-level modules (lib/domain/scan-safety,lib/config,app/manifest, …) or uses Vitest APIs the app no longer runs (vi.queueMock), so all 27 loadable files fail withERR_MODULE_NOT_FOUND; thetests/ui/*.tsx+tests/e2especs aren't even executed bytsx --test.Removed: the
tests/dir (37 files), the orphanedvitest.config.ts+playwright.config.ts, and the now-unused devDeps@playwright/test,@testing-library/jest-dom,@testing-library/react,vitest. Verified nothing insrc/imports them — all 38 current tests usenode:test.Result:
npm testgoes from 112/36 (or 129/35 with the prisma client generated) to 129 pass / 8 fail with zero module-not-found noise. The remaining 8 failures are pre-existing integration tests (library-import / slideshow / storage-paste) that need a liveDATABASE_URL— untouched by this PR; they pass against the media-organizer Postgres. Lint unchanged; CIdocker buildunchanged (still green).Heads-up (separate, optional): CI (
.forgejo/workflows/ci.yml) only runsdocker build— it does not runnpm test, which is why the earlier RSC bug (#41) and these stale tests slipped through. If you want, a follow-up can add a test job with a Postgres service container sonpm test(incl. the 8 integration tests) gates PRs.