5a430df5d9
* booker email verification changes * name type fix * use totp and code * prisma schema styling * refactor: code Signed-off-by: Udit Takkar <udit.07814802719@cse.mait.ac.in> * fix: book event form Signed-off-by: Udit Takkar <udit.07814802719@cse.mait.ac.in> * fix: type error Signed-off-by: Udit Takkar <udit.07814802719@cse.mait.ac.in> * fix: type errors Signed-off-by: Udit Takkar <udit.07814802719@cse.mait.ac.in> * fix: unit tests Signed-off-by: Udit Takkar <udit.07814802719@cse.mait.ac.in> * refactor: move verifycodedialog from ui and to features/bookings * fix: type error --------- Signed-off-by: Udit Takkar <udit.07814802719@cse.mait.ac.in> Co-authored-by: rkreddy99 <rreddy@e2clouds.com> Co-authored-by: Udit Takkar <udit.07814802719@cse.mait.ac.in> |
||
---|---|---|
.. | ||
lib | ||
.env.test.example | ||
README.md | ||
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