vikunja
/
frontend
4
29
Fork 37
Code Issues 89 Pull Requests 36 Releases 22 Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'main'
${ noResults }
frontend/cypress
History
Dominik Pschenitschni 96e2c81b7e
continuous-integration/drone/pr Build is passing Details
continuous-integration/drone/push Build is passing Details
fix: ignore ts deprecations for now 		1 hour ago
..
e2e fix: ignore ts deprecations for now 1 hour ago
factories feat: rename list to project everywhere 1 week ago
fixtures Frontend Testing With Cypress (#313) 2 years ago
support fix(cypress): use ts for updateUserSettings 3 months ago
README.md feat(cypress): use cy.session 3 months ago
docker-compose.yml feat(cypress): use cy.session 3 months ago

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

pnpm run test:e2e

Using The Cypress Dashboard

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

pnpm run test:e2e:dev