toHaveAccessibilityValue always truthy about jest-native HOT 4 CLOSED

@gkartalis in your example the View had accessibilityValue prop, but it did not have accessibilityState.
Matching of these two props has differences derived from React Native + iOS/Android accessibility behavior:

1. accessibilityValue matching relies on having exact matches, and on my machine it worked fine, as mentioned in my previous comment
2. accessibilityState matching relies on some implied states, e.g. by default each view is considered to be disabled: false unless explicitly specified otherwise. You can read details here

from jest-native.

@gkartalis not sure what exactly is happening at your side, so I'll do my best to address your issue.

I've spotted few errors in your test code:

1. disabled: true should be put inside accessibilityState and not accessibilityValue prop for View
2. First two expect (with accessibilityState) are also putting text in toHaveAccessibilityState which should be put in toHaveAccessibilityView. They are also the same, despite comments about one failing and other not.

The following test passes correctly on my side:

test('issue', () => {
  render(
    <View
      testID="view"
      accessibilityValue={{ text: 'Almost full' }}
      accessibilityState={{ disabled: true }}
    />
  );

  const view = screen.getByTestId('view');

  expect(view).toHaveAccessibilityState({ disabled: true });
  expect(view).not.toHaveAccessibilityState({ disabled: false });

  expect(view).toHaveAccessibilityValue({ text: 'Almost full' });
  expect(view).not.toHaveAccessibilityValue({ text: 'Whatever this is wrong' });
});

Let me know if correcting the spotted issues resolves the error for you. If not then pls prepare a minimal repro repository based on RNTL basic example, so that I can reproduce the issue locally.

from jest-native.

Gotcha, honestly I went ahead and thought thattoHaveAccessibilityValue is the same as toHaveAccessibilityState but partial for a single state value. That was also the reason that my example was like that.

I can now close the issue then, but the thing is that toHaveAccessibilityValue was not failing even though I didn't have any accessibilityValue prop included 🤔, any way closing the issue.

Thanks for the response!

from jest-native.

Good point good point it was an unfortunate typo :D . But thanks for the links (I will also edit the initial post to reflect that)

from jest-native.