Destructing render to get selectors binds result of render to selectors. Sometimes it's unwanted, especially if creating some reusable functions across the tests.
This binding is completely unnecessary, doesn't benefit tests readability and ease of development. It's easier to use screen everywhere, because of auto-completion and lack of maintenance of destructed properties.
Use screen instead of destructing render
:recycle: Current situation & Problem
Destructing
render
to get selectors binds result of render to selectors. Sometimes it's unwanted, especially if creating some reusable functions across the tests.This binding is completely unnecessary, doesn't benefit tests readability and ease of development. It's easier to use
screen
everywhere, because of auto-completion and lack of maintenance of destructed properties.:gear: Release Notes
Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: