Nav bar testing #64
Merged
Nav bar testing #64
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change:
Why is this change required? What problem(s) does it solve?
Adds a unit test for the NavBar
Were there any challenges while implementing this feature? If so, how were they addressed?
We may want to update this once we start using the react-native-testing-library. Also , I wasn't able to rebase this branch because it kept overwriting my updates even though I pulled in changes from the origin master.
Where should the reviewer start? How can this be tested?
NavBar folder
Link issues
#49 in progress