Dominik Pschenitschni
e7a766800d
All checks were successful
continuous-integration/drone/pr Build is passing
the edit-task component is only used in the listview which doesn't make sense: either all views should have such quick-view mode or none. By removing this component we _do_ remove a bit of functionality. But: if we improve the modal of the taskdetailview it's general usability and add a new sidebar mode (instead of the current float-in-the-center we do have even a better solution |
||
---|---|---|
.. | ||
e2e | ||
factories | ||
fixtures | ||
support | ||
docker-compose.yml | ||
README.md | ||
tsconfig.json |
Frontend Testing With Cypress
Setup
- Enable the seeder api endpoint. You'll then need to add the testingtoken in
cypress.json
or set theCYPRESS_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:frontend
Using The Cypress Dashboard
To open the Cypress Dashboard and run tests from there, run
pnpm run cypress:open