-
-
Notifications
You must be signed in to change notification settings - Fork 130
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
test: add e2e tests for css modules #693
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
@himself65 Hi, would you be able to give a quick review please? |
btw, I was trying to add chromatic for visual test last year, forget to continue on this |
933f8e9
to
e851c66
Compare
e851c66
to
d86397f
Compare
Can you check CI errors? Are they understandable? |
Ah, you need to add a reference in |
I'm checking the final error so we can get this done |
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.
LGTM, maybe we need to abstract e2e setup script so we don't need to copy paste everything
I can work on that if you want |
This PR relates to #186. It adds e2e tests for CSS modules.
I used
expect .toContain('class-name')
because I was not sure if the generated name would always be the same.