-
Notifications
You must be signed in to change notification settings - Fork 0
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
Configure UI unit tests #167
Conversation
7e5b29d
to
f7088e5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thanks Stas! Were there any updates / modifications needed for server side components (we don't have many though right now if at all... been just trying to build first)? Or do you think it will just work as normal?
Great question, Kris! I do not have any experience with testing server side components yet but I believe that if they are not async server components, we should be able to test them with this setup. |
Sounds good! That totally makes sense - yeah, definitely no async server components yet. I was having some trouble getting ReactQuery to play with SSR generally which is why I went with client components for everything. I'd definitely like to revisit that though because that's sorta a big point of using Next I think.. |
Configures jest. Adds a couple of tests to verify that it can be run and modules could be mocked.
f7088e5
to
7893e1f
Compare
Configures Jest test runner with testing-library/react.
Adds a simple test to assistand-builder to verify that everything is working and can be mocked.
Updates Readme file. Adds UI Setup instructions.
Closes #169