-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
How to tap backbutton arrow created by react navigation ? #3375
Comments
@lisa-gogo please share your solution, if you have one 🙏🏻 |
@d4vidi sorry
'gobackbutton' is the testid of the go back arrow. |
Another solution I use is that I use multiple describe in one single e2e.js file.
|
Thanks, that's a good reference to have. In any case, there's always |
|
It's written in this very issue. Have a look. |
@d4vidi
works but it is very brittle because I might have multiple buttons and the back button is not the first button on the screen. Or is there any other solution that I missed |
This works for me as right swipe does the job of a back button in iOS. |
I tried all of the above and it did not work. Just in case anyone came across this, you can set custom |
THANK YOU @tranquanghuy0801 - You are a ⭐ |
In case anyone is using Maestro, I've also found that the |
Hey, could you give me an example of this? Where should I add this property exactly? |
You can set the value for export const customStackNavigationOptions: StackNavigationOptions = {
headerBackTestID: 'header-back',
....
}; |
Description
There are two buttons on this page.
One is on the top-left, which was created by react-navigation.
One is just 'confirmation' button.
I trying tapping the first top back button.
I use the code
not working, no match element for 'header-back;
I then use the code
not working too, it clicks 'confirmation button ' on the button page. not the top back button I want.
Your environment
Detox version:
React Native version:
Node version:
Device model:
OS:
Test-runner (select one): jest-circus / jest+jasmine / mocha / other
The text was updated successfully, but these errors were encountered: