-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Problem
Running npm test results in 9 test failures across 5 test suites.
Evidence
$ npm test
Test Suites: 5 failed, 2 passed, 7 total
Tests: 9 failed, 43 passed, 52 totalFailed Test Suites:
jest.setup.test.js__tests__/config/environment.test.ts__tests__/Home.test.tsx__tests__/components/ChatInterface.test.tsx__tests__/components/FileUpload.test.tsx
Root Cause Analysis
Tests are out of sync with the actual UI:
Test expects: "Dokument zum Lernen hochladen"
UI shows: "Datei hochladen"
The component text was changed but tests weren't updated.
Working Checks
- ✅
npm run build- Succeeds - ✅
npm run type-check- Succeeds - ✅ Live demo works: https://checkst-bot.vercel.app
Required Fixes
1. FileUpload.test.tsx
Update text matchers to match current UI:
// Before
expect(screen.getByText(/Dokument zum Lernen hochladen/i)).toBeInTheDocument();
// After
expect(screen.getByText(/Datei hochladen/i)).toBeInTheDocument();2. Review All Failed Tests
Each failed test needs to be checked against the current UI/behavior.
3. Consider Test Refactoring
- Use data-testid attributes instead of text matching
- This prevents tests from breaking when UI text changes
Impact
HIGH - Failing tests make CI/CD unreliable and signal poor code quality to recruiters reviewing the repo.
Priority
P1 - Must fix before showcasing as portfolio project.
This issue was created as part of portfolio cleanup for AI Automations SE applications.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working