How to test gesture config changes?

[Glazzes]

Hi, I have been trying to write some tests for my library however the documentation offers no relevant information at all about how to test this library and I feel lost, I'm currently trying to test whether a gesture has been disabled after some particular action.

Assuming we have a code like this one

const [isPanEnabled, setIsPanEnabled] = useState(true);
const pinch = Gesture.Pinch()
  .withTestId("pinch")
  .onStart(() => runOnJs(setIsPanEnabled)(false));

const pan = Gesture.Pan()
  .withTestId("pan")
  .enabled(isPanEnabled);

I need to check if the pan gesture has been disabled after the pinch gesture executed its onStart method, this is what I currently have.

test('disable all other gestures when pinch has started', () => {
    render(
      <View style={styles.root}>
        <ResumableZoom>
          <Image source={undefined} style={styles.image} />
        </ResumableZoom>
      </View>
    );

    act(() => {
      fireGestureHandler<PinchGesture>(getByGestureTestId('pinch'), [
        { state: State.BEGAN },
        { state: State.UNDETERMINED },
      ]);
      jest.runAllTimers();
    });

    const pan = getByGestureTestId('pan');
    expect(pan.config.enabled).toBe(false);
  });

At the moment I'm sure the onStart methods works fine, however when I retrieve the gesture it always returns a value with the value of pan.config.enable set to true when I expect it to be false.

Hope someone can help, thanks.

[AlakhiarovSalekh]

There are two separate issues in the example.
First, the event sequence never activates the pinch gesture. onStart runs when the gesture becomes ACTIVE, but the example sends BEGAN -> UNDETERMINED. Try an actual lifecycle such as:
act(() => {
fireGestureHandler(getByGestureTestId('pinch'), [
{ state: State.BEGAN },
{ state: State.ACTIVE },
{ state: State.END },
]);
});

Second, I would avoid asserting pan.config.enabled directly. The object returned by getByGestureTestId should effectively be treated as test infrastructure/opaque gesture data rather than a public configuration-inspection API.
A more robust test is to assert the observable result of your state change after the pinch starts. If you specifically need to prove that the native recognizer refuses to activate when .enabled(false) is applied, Jest is not the best level for that test: the RNGH Jest helpers simulate gesture callback lifecycles; they do not reproduce the complete native gesture-recognizer arbitration.
So I would:

1. unit-test that starting the pinch changes the React state that controls enabled;
2. separately use an integration/E2E test if you need to verify native recognition behavior.