vynte-infra/calendar
2
0
Fork 0
Code Issues Pull Requests Actions 1.1k Packages Projects Releases Wiki Activity
Files
3a4ebadbf39262c60d5c853fbc466c0453e1c8e6
calendar/apps/web/test
T
History
Syed Ali ShahbazGitHubPeer RichelsenPeer Richelsensean-brydonsean-brydon
 3a4ebadbf3 feat: track no-shows in bookings (#15307) 
* added dropdown for no-shows in past bookings

* added layout

* nit

* todo comment: figure out how to close dropdown

* more todo comments

* Adds TRPC route among other WIP

* functional update

* fixes type err

* fix type err

* fix: styles

* strikethrough in email

* NITs

* removed stale comment

* add tests

* err comment

---------

Co-authored-by: Peer Richelsen <peer@cal.com>
Co-authored-by: Peer Richelsen <peeroke@gmail.com>
Co-authored-by: sean-brydon <sean@cal.com>
Co-authored-by: sean-brydon <55134778+sean-brydon@users.noreply.github.com>
2024-06-04 15:18:11 +00:00
..
fixtures
test: add unit tests for sms sending (#14737)
2024-05-02 10:42:38 -04:00
handlers
feat: track no-shows in bookings (#15307)
2024-06-04 15:18:11 +00:00
lib
fix: Booking Error - cannot be booked at this time (#15288)
2024-06-04 15:09:57 +00:00
utils/bookingScenario
fix: Booking Error - cannot be booked at this time (#15288)
2024-06-04 15:09:57 +00:00
.env.test.example
Add getSchedule tests (#3233)
2022-07-21 10:44:23 -06:00
docker-compose.yml
chore: prettier
2023-08-15 11:59:16 -07: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
Feat/design system (#3051)
2022-07-22 18:39:50 -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

Reference in New Issue View Git Blame Copy Permalink