History

kolaente 2e3b2cb770 fix: ensure project filters are retained correctly across views (#1643 )		2025-11-16 14:29:50 +00:00
..
e2e	fix: ensure project filters are retained correctly across views (#1643 )	2025-11-16 14:29:50 +00:00
factories	fix(test): prune leftover task duplicates	2025-09-30 16:50:11 +02:00
fixtures	chore: move frontend files	2024-02-07 14:56:56 +01:00
support	fix: ensure project filters are retained correctly across views (#1643 )	2025-11-16 14:29:50 +00:00
README.md	docs: fix typos	2025-06-10 12:10:42 +02:00
docker-compose.yml	chore(deps): update cypress/browsers:latest docker digest to e85371f (#1798 )	2025-11-12 21:08:47 +01:00

README.md

Frontend Testing With Cypress

Setup

Enable the seeder api endpoint. You'll then need to add the testingtoken in cypress.json or set the CYPRESS_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 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