Cannot check if an element is disabled after updating to v7

Describe the bug

In v6.0.0, I was able to check if an element had a disabled prop like this: expect(element.props.disabled).toBeTruthy(), but since I updated to v7.0.1, the disabled attribute is no longer in the element.

Expected behavior

I would like to check if an element is disabled or not

Steps to Reproduce

Render a <TouchableOpacity disabled /> component and then try to check if it is disabled with expect(element.props.disabled).toBeTruthy()

Versions

@testing-library/react-native: ^7.0.1 => 7.0.1 
react: ~16.11.0 => 16.11.0 
react-native: https://github.com/expo/react-native/archive/sdk-38.0.2.tar.gz => 0.62.2 

[JoseLion]

@thymikee that does not really solve the problem. Most of the time you’ll not be able to change the onPress prop for a spy because usually, we’d want to test buttons deep within a screen.

As a workaround, I implemented a helper function that checks if onStartShouldSetResponder is implemented and has the pressablility config present:

export function isDisabled(element: Nullable<ReactTestInstance>): boolean {
  return !!element?.props.onStartShouldSetResponder?.testOnly_pressabilityConfig()?.disabled;
}

Then in a spec

expect(isDisabled(getByText("Cancel")).toEqual(false);

expect(isDisabled(getByText("Continue")).toEqual(true);

[JoseLion]

While jest-native is great, we could not be using it on a project. We could not be even using Jest and testing with Mocha for instance (which is possible and fairly easy to achieve 😅).

IMHO, I think it’ll be better if this issue is addressed right from RNTL. I think this is not just an assertion convenience, it’s usually very important to tests that interactions are enable or disabled for a user 🙂

It’d be great if this issue can be reopened 😀