-
-
Notifications
You must be signed in to change notification settings - Fork 829
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
Frontend tests #3990
Comments
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While tests are very helpful, too many tests, or too intensive tests make the code hard and more cumbersome to change. So what we need are rather basic tests for components, and when appropriate (like extenders or utils/helpers) more in-depth tests.
Striking a balance between sufficient test coverage and maintainability is crucial here.
The most basic test we can have for a component, yet can still be useful, is that it simply renders without issues and some interactions (such as any clicks) work as expected.
We'll prioritize components that are building blocks of other components.
Then Utils/Helpers that are most commonly used.
Then Extenders.
And finally Large components. (integration tests if possible)
Building Blocks
Tooltip(tied to jquery so skipping for now)Utils/Helpers
Extenders
Larger components
IndexPage
if possibleRelevant links, should be documented with the docs we will add for frontend testing:
Must also add the
Jest
infra generation to the CLI.The text was updated successfully, but these errors were encountered: