component.props.onChange' is undefined about cavy HOT 3 CLOSED

Glad you got it working accessing the onValuesChange prop!

Re your second question, there are two types of components you need to wrap in order to test it's props:

1. A function component (as explained in the docs)
2. Some of React Native's basic components like <Text> and <TextInput>. This is unfortunately due to React Native restructuring some of it's core components (this blog post explains it well). In short, when you add a ref to these components, React Native are now forwarding it so that a Native component is returned and not the React Native component itself. This means that the JS props are not for Cavy to call from within tests.

The current solution is to wrap these components so that Cavy can obtain a reference to these props. It's not ideal, but we're working on a solution at the moment that means you don't have to do this :)

from cavy.

Realized I had a typo for my failed test onValuesChange and not onChange.

Also realized that I don't need to wrap the slider to access onValuesChange.

But, now I am wondering why it is necessary to wrap react-native components. I see this note in the documentation (which is neither a React Class nor a Function Component) but am trying to better understand how they are not a React Class.

For example <View> in the definition extends ViewBase which is a typeof ViewComponent that extends React.Component<ViewProps>

from cavy.

Closing for now as I don't think there was an issue, but feel free to ask questions on here / continue the discussion.

from cavy.