mirror of
https://github.com/go-vikunja/vikunja.git
synced 2026-04-25 22:55:06 +00:00
8a4e43fb96
- Add loading state waits to 'Marks a task as done' test - Add loading state waits to navigation tests: - 'provides back navigation to the project in the list view' - 'provides back navigation to the project in the table view' - 'provides back navigation to the project in the kanban view on mobile' - 'does not provide back navigation to the project in the kanban view on desktop' - These fixes prevent CypressError where task elements have CSS pointer-events: none - All tests now wait for .is-loading class removal before attempting element interactions - Comprehensive coverage of task interaction patterns that were causing CI failures 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
Frontend Testing With Cypress
Setup
- Enable the seeder api endpoint. You'll then need to add the testingtoken in
cypress.jsonor set theCYPRESS_TEST_SECRETenvironment variable. - Basic configuration happens in the
cypress.jsonfile - Overridable with env
- Override base url with
CYPRESS_BASE_URL
Fixtures
We're using the test endpoint of the vikunja api to seed the database with test data before running the tests. This ensures better reproducibility of tests.
Running The Tests Locally
Using Docker
The easiest way to run all frontend tests locally is by using the docker-compose file in this repository.
It uses the same configuration as the CI.
To use it, run
docker-compose up -d
Then, once all containers are started, run
docker-compose run cypress bash
to get a shell inside the cypress container. In that shell you can then execute the tests with
pnpm run test:e2e
Using The Cypress Dashboard
To open the Cypress Dashboard and run tests from there, run
pnpm run test:e2e:dev