83c8f97afd
* test: booking and frequency limits e2e * test: refactor limit e2e and check multiple * test: move limits e2e to separate file * fix: blocked day assertions * chore: rename to booking-limits * fix: use todo test util * chore: un-DRY tests * feat: create user with limits helper * chore: move user limit helper to utils * fix: multiple limits test * feat: fail faster * chore: event url helper * fix: prismock count date comparisons * chore: improve booking limit types in test utils * test: add typed weekStart to getOrganizer helper * test: add custom fromDate to getDate helper * fix: correctly handle negative date increments * test: add helper for partial weeks * test: booking limits edge cases * chore: remove booking limit e2e todos * chore: normalize getDate return type and skip test * Fix imports paths that are changes after main merge * Fix failing types * Skip failing test --------- Co-authored-by: Peer Richelsen <peeroke@gmail.com> Co-authored-by: Keith Williams <keithwillcode@gmail.com> Co-authored-by: Alex van Andel <me@alexvanandel.com> Co-authored-by: Hariom <hariombalhara@gmail.com> |
||
---|---|---|
.. | ||
fixtures | ||
handlers | ||
lib | ||
utils/bookingScenario | ||
.env.test.example | ||
docker-compose.yml | ||
jest-resolver.js | ||
jest-setup.js | ||
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