This repository has been archived on 2024-02-08. You can view files and clone it, but cannot push or open issues or pull requests.
kolaente 803f9c81c2
Some checks failed
continuous-integration/drone/pr Build is failing
fix(editor): make tests work with changed structure
2023-10-22 14:21:28 +02:00
..
e2e fix(editor): make tests work with changed structure 2023-10-22 14:21:28 +02:00
factories feat(reminders): add e2e tests for task reminders 2023-06-20 15:56:39 +02:00
fixtures Frontend Testing With Cypress (#313) 2020-12-10 13:52:35 +00:00
support feat(reminders): add e2e tests for task reminders 2023-06-20 15:56:39 +02:00
docker-compose.yml feat(cypress): use cy.session 2023-01-03 16:30:46 +01:00
README.md feat(cypress): use cy.session 2023-01-03 16:30:46 +01:00

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