.

Author: mdjastrzebski

website/docs/12.x/docs/api.md

@@ -1,6 +1,7 @@
 ---
 uri: /api
 ---
+
 # API Overview
 
 React Native Testing Library consists of following APIs:
@@ -12,10 +13,9 @@ React Native Testing Library consists of following APIs:
   - Helpers: [`debug`](docs/api/screen#debug), [`toJSON`](docs/api/screen#tojson), [`root`](docs/api/screen#root)
 - [Jest matchers](docs/api/jest-matchers) - validate assumptions about your UI
 - [User Event](docs/api/events/user-event) - simulate common user interactions like [`press`](docs/api/events/user-event#press) or [`type`](docs/api/events/user-event#type) in a realistic way
-- [Fire Event](docs/api/events/fire-event) - simulate any component event in a simplified way
-purposes
+- [Fire Event](docs/api/events/fire-event) - simulate any component event in a simplified way purposes
 - Misc APIs:
-  - [`renderHook` function](docs/api/misc/render-hook) - render hooks for testing 
+  - [`renderHook` function](docs/api/misc/render-hook) - render hooks for testing
   - [Async utils](docs/api/misc/async): `findBy*` queries, `wait`, `waitForElementToBeRemoved`
   - [Configuration](docs/api/misc/config): `configure`, `resetToDefaults`
   - [Accessibility](docs/api/misc/accessibility): `isHiddenFromAccessibility`

website/docs/13.x/docs/advanced/_meta.json

@@ -1 +1 @@
-["testing-env", "understanding-act"]
+["testing-env", "understanding-act", "third-party-integration"]

website/docs/13.x/docs/advanced/third-party-integration.mdx

@@ -0,0 +1,39 @@
+# Third-Party Library Integration
+
+The React Native Testing Library is designed to simulate the core behaviors of React Native. However, it does not replicate the internal logic of third-party libraries. This guide explains how to integrate your library with RNTL.
+
+## Handling Events in Third-Party Libraries
+
+RNTL provides two subsystems to simulate events:
+
+- **Fire Event**: A lightweight simulation system that can trigger event handlers defined on both host and composite components.
+- **User Event**: A more realistic interaction simulation system that can trigger event handlers defined only on host components.
+
+In many third-party libraries, event handling involves native code, which means RNTL cannot fully simulate the event flow, as it runs only JavaScript code. To address this limitation, you can use `testOnly_on*` props on host components to expose custom events to RNTL’s event subsystems. Both subsystems will first attempt to locate the standard `on*` event handlers; if these are not available, they fall back to the `testOnly_on*` handlers.
+
+### Example: React Native Gesture Handler
+
+React Native Gesture Handler (RNGH) provides a composite [Pressable](https://docs.swmansion.com/react-native-gesture-handler/docs/components/pressable/) component with `onPress*` props. These event handlers are not exposed on the rendered host views; instead, they are invoked via RNGH’s internal event flow, which involves native modules. As a result, they are not accessible to RNTL’s event subsystems.
+
+To enable RNTL to interact with RNGH’s `Pressable` component, the library exposes `testOnly_onPress*` props on the `NativeButton` host component rendered by `Pressable`. This adjustment allows RNTL to simulate interactions during testing.
+
+```tsx title="Simplified RNGH Pressable component"
+function Pressable({ onPress, onPressIn, onPressOut, onLongPress, ... }) {
+
+  // Component logic...
+
+  const isTestEnv = process.env.NODE_ENV === 'test';
+
+  return (
+    <GestureDetector gesture={gesture}>
+      <NativeButton
+        /* Other props... */
+        testOnly_onPress={isTestEnv ? onPress : undefined}
+        testOnly_onPressIn={isTestEnv ? onPressIn : undefined}
+        testOnly_onPressOut={isTestEnv ? onPressOut : undefined}
+        testOnly_onLongPress={isTestEnv ? onLongPress : undefined}
+      />
+    </GestureDetector>
+  );
+}
+```

website/docs/13.x/docs/api.md

@@ -1,6 +1,7 @@
 ---
 uri: /api
 ---
+
 # API Overview
 
 React Native Testing Library consists of following APIs:
@@ -12,10 +13,9 @@ React Native Testing Library consists of following APIs:
   - Helpers: [`debug`](docs/api/screen#debug), [`toJSON`](docs/api/screen#tojson), [`root`](docs/api/screen#root)
 - [Jest matchers](docs/api/jest-matchers) - validate assumptions about your UI
 - [User Event](docs/api/events/user-event) - simulate common user interactions like [`press`](docs/api/events/user-event#press) or [`type`](docs/api/events/user-event#type) in a realistic way
-- [Fire Event](docs/api/events/fire-event) - simulate any component event in a simplified way
-purposes
+- [Fire Event](docs/api/events/fire-event) - simulate any component event in a simplified way purposes
 - Misc APIs:
-  - [`renderHook` function](docs/api/misc/render-hook) - render hooks for testing 
+  - [`renderHook` function](docs/api/misc/render-hook) - render hooks for testing
   - [Async utils](docs/api/misc/async): `findBy*` queries, `wait`, `waitForElementToBeRemoved`
   - [Configuration](docs/api/misc/config): `configure`, `resetToDefaults`
   - [Accessibility](docs/api/misc/accessibility): `isHiddenFromAccessibility`

website/docs/13.x/docs/guides/_meta.json

@@ -1 +1 @@
-["how-to-query", "troubleshooting", "faq", "community-resources", "third-party-integration"]
+["how-to-query", "troubleshooting", "faq", "community-resources"]