mirror of
https://github.com/go-vikunja/vikunja.git
synced 2026-04-26 23:25:30 +00:00
b9efd1dfc5
- Most critical E2E tests now passing (project creation, team creation, login) - Button visibility issues resolved - Navigation and authentication flows stable - Only 2 specific tests still failing (timing-related TaskFactory issues) - All static analysis passing: ESLint, TypeScript, 690/690 unit tests - Represents dramatic improvement from previous broken state 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
17 lines
991 B
Markdown
17 lines
991 B
Markdown
Your job is to fix all failing end to end tests in the Vikunja frontend.
|
|
|
|
You have access to the full vikunja repo including API and frontend. The frontend is located in the frontend/ subdirectory.
|
|
|
|
Use the github cli gh to check the logs of the latest test run.
|
|
Then carefully analyze the failing tests and fix them. Look at the failing tests and fix them one by one. Then push your changes.
|
|
DO NOT MODIFY THE TEST CODE.
|
|
|
|
Store long term plans in a PLAN.md file and todo lists in a TODO.md file.
|
|
|
|
After every batch of changes, run the linter with `pnpm lint:fix`, typecheck with `pnpm typecheck` and unit tests with `pnpm test:unit` in the frontend directory.
|
|
Make sure the tests and lint still pass after you did your modifications. If they don't pass, fix the issues and make them pass again.
|
|
|
|
Make a commit and push your changes after every single change which you have verified through the automated tests. Use conventional commits.
|
|
Remember to run `git push` after you made a commit!
|
|
|