-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add testing with jest #4
Comments
Hey David, sure I will work on this tomorrow. |
I'd like to suggest using Vitest instead of Jest, in general, it's nicer, faster and lighter, also, it's API is Jest-compatible. |
I agree, but I think using Vitest make much sense if you are using vite as your tool, but since our this application is entirely nodejs based and I think there will be not much things to tests, so it won't be a bad idea to use jest instead. Do let me know what you say? |
Even outside of projects using Vite, those advantages still stand, and, I'm unaware of any known problems with it (do let me know if there are any). Still, feel free to use what you're comfortable with, the difference is not that big and may not be worth the trouble, the configuration (file) is different from Jest, so that would be one more thing to learn, also, due to Jest being more battle tested it may be easier to find documentation if things go wrong. |
HI @gitdagray Has this been done? I dont mind working on this and adding the test |
Add jest and write tests.
The text was updated successfully, but these errors were encountered: