History

Dominik Pschenitschni 3b9bc5b2f8 feat: use BaseButton where easily possible This replaces links with BaseButton components. BaseButton will use `<button type="button">` inside for this case. This improves accessibility a lot. Also we might be able to remove the `.stop` modifiers in some places because AFAIK the button element stops propagation by default.		2022-07-06 21:07:26 +00:00
..
e2e	feat: use BaseButton where easily possible	2022-07-06 21:07:26 +00:00
factories	chore: rename js files to ts	2022-07-04 21:50:48 +00:00
fixtures	Frontend Testing With Cypress (#313 )	2020-12-10 13:52:35 +00:00
support	fix: cypress plugins	2022-07-04 21:50:48 +00:00
docker-compose.yml	chore: change cypress settings to run tests in cypress without needing to modify the config	2021-10-02 20:07:38 +02:00
README.md	chore: some small changes in the cypress README.md (#793 )	2021-09-26 17:49:27 +00:00
tsconfig.json	feat: setup cypress	2022-07-04 21:50:48 +00: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

yarn test:frontend

Using The Cypress Dashboard

To open the Cypress Dashboard and run tests from there, run

yarn cypress:open