cal.pub0.org/apps/web/test
Leo Giovanetti 734382b5b3
refactor: Moving from jest to vitest (#9035)
* Moving to vitest

* Rearranging test

* Fixing prettier linting

* Reverting launch.json

* Adjustments

* Merged with main and regenerated lockfile

* Fixing tests for API

* Yarn updated, docs is gone

---------

Co-authored-by: Peer Richelsen <peeroke@gmail.com>
Co-authored-by: zomars <zomars@me.com>
Co-authored-by: Alex van Andel <me@alexvanandel.com>
2023-05-24 23:35:44 +00:00
..
lib refactor: Moving from jest to vitest (#9035) 2023-05-24 23:35:44 +00:00
.env.test.example Add getSchedule tests (#3233) 2022-07-21 10:44:23 -06:00
README.md Feat/design system (#3051) 2022-07-22 18:39:50 -06:00
docker-compose.yml Add getSchedule tests (#3233) 2022-07-21 10:44:23 -06:00
jest-resolver.js Update all Yarn dependencies (2022-07-29) (#3599) 2022-08-17 11:38:21 -06:00
jest-setup.js Update all Yarn dependencies (2022-07-29) (#3599) 2022-08-17 11:38:21 -06:00

README.md

Unit and Integration Tests

Make sure you have copied .env.test.example to .env.test

You can run all jest tests as

yarn test

You can run tests matching specific description by following command yarn test -t getSchedule

Tip: Use --watchAll flag to run tests on every change