-
Notifications
You must be signed in to change notification settings - Fork 274
docs: testing environment #1195
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
Conversation
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.
Very clear and well written, nice!
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.
Really interesting doc, I think it's a great addition ! I'm just not sure the tree navigation part is relevant, users should be able to use only RNTL api or @testing-library/jest-native matchers to write tests, even though understanding how it works is definitely useful
Co-authored-by: Pierre Zimmermann <64224599+pierrezimmermannbam@users.noreply.github.com> Co-authored-by: Augustin Le Fèvre <augustin.le-fevre@klarna.com>
@thymikee @AugustinLF @pierrezimmermannbam I've moved document to new |
@mdjastrzebski did you push your new commit?^^' I don't understand where this |
@AugustinLF LOL, nope ;-) |
Summary
This docs describes in simple terms how our testing environment operates, so that our users can learn more on behaviour and limitations of using RNTL.
Test plan
None