You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't wanna test implementation details here, so when writing tests we should focus on how the component behaves, so when props or method names change, the test must still pass
Don't worry so much about testing coverage, it's just a metric and the important thing is to cover how the component is being actually used
Avoid testing using snapshots, but if you really wanna use them, please read this article before
Each component should have a separate PR, If you decide to start writing tests for some of the components listed above, please drop a comment on this issue so we can keep track of everything :)
The text was updated successfully, but these errors were encountered:
Hello, I would like to give this a try! Would I be able to try with the Avatar component? I'm new to unit testing, but I am interested in giving it a shot
In order to have a stable codebase, we need to properly unit test our core UI components.
For doing so, we're using the
react-native-testing-library
, which encourages best practices when testing React Native components.List of components that need to be tested:
Avatar
Button
BottomSheet
Control
Header
ListItem
Modal
Notification
TextInput
Definition of done
Each component should have a separate PR, If you decide to start writing tests for some of the components listed above, please drop a comment on this issue so we can keep track of everything :)
The text was updated successfully, but these errors were encountered: