History

kolaente 7991bee6ac chore(test): cleanup and improve e2e tests		2025-05-20 16:57:26 +02:00
..
e2e	chore(test): cleanup and improve e2e tests	2025-05-20 16:57:26 +02:00
factories	fix(auth): only use query parameters instead of local storage for password reset token (#770 )	2025-05-14 20:51:45 +00:00
fixtures	chore: move frontend files	2024-02-07 14:56:56 +01:00
support	fix(editor): make pasting a file work again	2025-05-20 16:57:26 +02:00
README.md	chore: move frontend files	2024-02-07 14:56:56 +01:00
docker-compose.yml	fix(deps): pin dependencies (#435 )	2025-03-31 17:35:22 +02: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 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