Dominik Pschenitschni
60f58af41a
continuous-integration/drone/pr Build is passing
Details
continuous-integration/drone/push Build is passing
Details
Changes only in task detail view. Probably this should be done everywhere: - some buttons were using the uppercase words consistently, some were not - some were using articles, some were not => I removed them everywhere to shorten the label length - some buttons were refering to the task, some were not. Since we are already in the context of the task (we are not the task detail page) I removed the reference everywhere. |
||
|---|---|---|
| .. | ||
| factories | ||
| fixtures | ||
| integration | ||
| plugins | ||
| 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
yarn test:frontend
Using The Cypress Dashboard
To open the Cypress Dashboard and run tests from there, run
yarn cypress:open