
fix: project table view fix: e2e tests fix: typo in readme fix: list view route fix: don't wait until background is loaded for list to show fix: rename component imports fix: lint fix: parse task text fix: use list card grid fix: use correct class names fix: i18n keys fix: load project fix: task overview fix: list view spacing fix: find project fix: setLoading when updating a project fix: loading saved filter fix: project store loading fix: color picker import fix: cypress tests feat: migrate old list settings chore: add const for project settings fix: wrong projecten rename from lists chore: rename unused variable fix: editor list fix: shortcut list class name fix: pagination list class name fix: notifications list class name fix: list view variable name chore: clarify comment fix: i18n keys fix: router imports fix: comment chore: remove debugging leftover fix: remove duplicate variables fix: change comment fix: list view variable name fix: list view css class name fix: list item property name fix: name update tasks function correctly fix: update comment fix: project create route fix: list view class names fix: list view component name fix: result list class name fix: animation class list name fix: change debug log fix: revert a few navigation changes fix: use @ for imports of all views fix: rename link share list class fix: remove unused css class fix: dynamically import project components again
Frontend Testing With Cypress
Setup
- Enable the seeder api endpoint. You'll then need to add the testingtoken in
cypress.json
or set theCYPRESS_TEST_SECRET
environment variable. - Basic configuration happens in the
cypress.json
file - 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 reproducability 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