Remove demo.spec.ts scaffold leftover from frontend test suite #125

Closed
opened 2026-03-27 18:36:35 +01:00 by marcel · 1 comment
Owner

Problem

frontend/src/demo.spec.ts contains a single test:

it('adds 1 + 2 to equal 3', () => {
  expect(1 + 2).toBe(3);
});

This is a scaffold file generated by npm create svelte and was never removed. It tests arithmetic, not the application.

Why This Matters

A test suite with meaningless tests is harder to trust. This file:

  • Inflates the test count
  • Wastes CI time (small, but the principle matters)
  • Creates noise in coverage reports

Fix

Delete frontend/src/demo.spec.ts.

That's it. One file, one line change.

Acceptance Criteria

  • frontend/src/demo.spec.ts deleted
  • npm test still passes
## Problem `frontend/src/demo.spec.ts` contains a single test: ```typescript it('adds 1 + 2 to equal 3', () => { expect(1 + 2).toBe(3); }); ``` This is a scaffold file generated by `npm create svelte` and was never removed. It tests arithmetic, not the application. ## Why This Matters A test suite with meaningless tests is harder to trust. This file: - Inflates the test count - Wastes CI time (small, but the principle matters) - Creates noise in coverage reports ## Fix Delete `frontend/src/demo.spec.ts`. That's it. One file, one line change. ## Acceptance Criteria - [ ] `frontend/src/demo.spec.ts` deleted - [ ] `npm test` still passes
marcel added the test label 2026-03-27 18:45:11 +01:00
Author
Owner

Architect review (@mkeller): Do this today. One file, zero risk, no discussion needed. A test suite with a test that checks 1 + 2 === 3 is harder to trust than one without it.

**Architect review (@mkeller):** ✅ Do this today. One file, zero risk, no discussion needed. A test suite with a test that checks `1 + 2 === 3` is harder to trust than one without it.
Sign in to join this conversation.
No Label test
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: marcel/familienarchiv#125