feat(native): Add toContainElement() #146
Conversation
| .toHaveMessage("Expected element <View ... /> to contain element <Text ... />."); | ||
| }); | ||
| }); | ||
| }); |
There was a problem hiding this comment.
Could we please add some tests for when there are no child nor parent elements 🙏
There was a problem hiding this comment.
Thanks for the recommendation! To take this into account, I've changed the structure of the tests so they're clearer and easier to read 🚀
| } | ||
|
|
||
| return ( | ||
| parentElement.findAll( |
There was a problem hiding this comment.
You can use the .some() method instead of finding all elements and then checking if the length is > 0 🙂
There was a problem hiding this comment.
@JoseLion .some does not exist on ReactInstance class. It is not an array
| <View testID="grandParentId"> | ||
| <View testID="parentId"> | ||
| <View testID="childId" /> | ||
| </View> | ||
| <Text testID="textId" /> | ||
| </View>, |
There was a problem hiding this comment.
Can we use <Text> elements so that we can avoid the testIDs?
There was a problem hiding this comment.
Im trying to do this, but im not getting good results, would you like to pair?
| describe (".toContainElement", () => { | ||
| const element = render( |
There was a problem hiding this comment.
As a good practice, elements should be rendered on each test it(..) function, so the cleanup function cleans what's rendered before each test, avoid flaky tests, etc.
kdquistanchala
force-pushed
the
feat/native-to-be-visible
branch
from
35e5052 to
82fa78b
Compare
lopenchi
force-pushed
the
feat/native-to-contain-element
branch
2 times, most recently
from
1942629 to
4194055
Compare
lopenchi
force-pushed
the
feat/native-to-be-visible
branch
from
4cfe69c to
dcded59
Compare
lopenchi
force-pushed
the
feat/native-to-contain-element
branch
from
4194055 to
392d9c6
Compare
This PR adds the
toContainElement()matcher for React Native