I\'m using react-navigation in my React Native project that I\'m setting up automated testing for using Detox.
Unfortunately, I don\'t see anything in the docs about
In case you are adding in the wrong place, try moving it to createBottomTabNavigator
createBottomTabNavigator(
{
YourStackLabel: {
screen: YourStackNavigator,
navigationOptions: {
tabBarTestID: "yourBottomBarButtonTestId",
},
},
}
);
I had a similar issue when using react-navigation in my app. I am currently using react-navigation 2.2.0.
Firstly I tried the following:
await element(by.label('Tab Name')).tap();
This worked and I was quite happy until I tried a different tab to go to, where the tab name matched a text item on the page, this meant there were two labels with the same text and Detox got confused. So using by.label
is only useful when you can guarantee that there is one instance of that label on the page.
The way I found to get around this was to set the tabBarTestID
navigations options for the screen. As long as you use unique ids then there should be no collisions.
Setting the tabBarTestID
can be done like so in your screen component:
class TabScreen extends Component {
static navigationOptions = () => {
return {
title: 'Tab Name',
tabBarLabel: 'Tab Name',
tabBarAccessibilityLabel: 'Tab Name',
tabBarTestID: 'Tab Name',
tabBarIcon: ({ tintColor, focused }) => {
return getTabIcon('Tab Name', focused);
}
};
};
render () {
return (
<View>
...
</View>
);
}
}
export default TabScreen;
This means you should should now be able, in your tests, to use:
await element(by.id('Tab Name')).tap();
It's all in the docs (almost)