021d71b90e
This removes date-fns and replaces it with the already used dayjs library. It does not make sense to have two libraries for the same purpose, and dayjs seems to be smaller and its translations are already integrated. Since we have to use dayjs because it is used by the gantt chart, this was the obvious way to go (instead of replacing dayjs with date-fns). Resolves https://github.com/go-vikunja/vikunja/issues/391 Reviewed-on: https://kolaente.dev/vikunja/vikunja/pulls/3039 Co-authored-by: kolaente <k@knt.li> Co-committed-by: kolaente <k@knt.li> |
||
|---|---|---|
| .. | ||
| e2e | ||
| factories | ||
| fixtures | ||
| support | ||
| README.md | ||
| docker-compose.yml | ||
README.md
Frontend Testing With Cypress
Setup
- Enable the seeder api endpoint. You'll then need to add the testingtoken in
cypress.jsonor set theCYPRESS_TEST_SECRETenvironment variable. - Basic configuration happens in the
cypress.jsonfile - 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