docs

Author: mdjastrzebski

website/docs/14.x/docs/advanced/testing-env.mdx

@@ -18,11 +18,11 @@ React allows you to write declarative code using JSX, write function or class co
 
 When you run your tests in the React Native Testing Library, somewhat contrary to what the name suggests, they are actually **not** using React Native renderer. This is because this renderer needs to be run on an iOS or Android operating system, so it would need to run on a device or simulator.
 
-## Universal Test Renderer
+## Test Renderer
 
-Instead, RNTL uses [Universal Test Renderer](https://github.com/mdjastrzebski/test-renderer), a modern, actively maintained renderer that allows rendering to pure JavaScript objects without access to mobile OS and can run in a Node.js environment using Jest (or any other JavaScript test runner). Universal Test Renderer replaces the deprecated `react-test-renderer` package and provides better compatibility with React 19 and improved type safety.
+Instead, RNTL uses [Test Renderer](https://github.com/mdjastrzebski/test-renderer), a modern, actively maintained renderer that allows rendering to pure JavaScript objects without access to mobile OS and can run in a Node.js environment using Jest (or any other JavaScript test runner). Test Renderer replaces the deprecated `react-test-renderer` package and provides better compatibility with React 19 and improved type safety.
 
-Using Universal Test Renderer has pros and cons.
+Using Test Renderer has pros and cons.
 
 Benefits:
 
@@ -41,9 +41,9 @@ It's worth noting that the React Testing Library (web one) works a bit different
 
 ## Element tree
 
-Calling the `render()` function creates an element tree. This is done internally by invoking the renderer's `create()` method from Universal Test Renderer. The output tree represents your React Native component tree, and each node of that tree is an "instance" of some React component (to be more precise, each node represents a React fiber, and only class components have instances, while function components store the hook state using fibers).
+Calling the `render()` function creates an element tree. This is done internally by invoking the renderer's `create()` method from Test Renderer. The output tree represents your React Native component tree, and each node of that tree is an "instance" of some React component (to be more precise, each node represents a React fiber, and only class components have instances, while function components store the hook state using fibers).
 
-These tree elements are represented by `HostElement` type from Universal Test Renderer:
+These tree elements are represented by `HostElement` type from Test Renderer:
 
 ```tsx
 interface HostElement {
@@ -56,7 +56,7 @@ interface HostElement {
 }
 ```
 
-For more details, see the [Universal Test Renderer documentation](https://github.com/mdjastrzebski/test-renderer).
+For more details, see the [Test Renderer documentation](https://github.com/mdjastrzebski/test-renderer).
 
 ## Host and composite components
 

website/docs/14.x/docs/api/render.mdx

@@ -45,11 +45,11 @@ Otherwise, `render` will default to using concurrent rendering used in the React
 createNodeMock?: (element: React.Element) => unknown,
 ```
 
-This option allows you to pass `createNodeMock` option to the renderer's `create()` method in order to allow for custom mock refs. This option is passed through to [Universal Test Renderer](https://github.com/mdjastrzebski/test-renderer).
+This option allows you to pass `createNodeMock` option to the renderer's `create()` method in order to allow for custom mock refs. This option is passed through to [Test Renderer](https://github.com/mdjastrzebski/test-renderer).
 
 :::note Text string validation
 
-Universal Test Renderer automatically enforces React Native's requirement that text strings must be rendered within a `<Text>` component. If you try to render a `string` value under components other than `<Text>` (e.g., under `<View>`), it will throw an `Invariant Violation: Text strings must be rendered within a <Text> component` error, matching React Native's runtime behavior.
+Test Renderer automatically enforces React Native's requirement that text strings must be rendered within a `<Text>` component. If you try to render a `string` value under components other than `<Text>` (e.g., under `<View>`), it will throw an `Invariant Violation: Text strings must be rendered within a <Text> component` error, matching React Native's runtime behavior.
 
 This validation is always enabled and cannot be disabled, ensuring your tests accurately reflect how your code will behave in production.
 

website/docs/14.x/docs/api/screen.mdx

@@ -148,7 +148,7 @@ Get the rendered component JSON representation, e.g. for snapshot testing.
 const container: HostElement;
 ```
 
-Returns a pseudo-element container whose children are the elements you asked to render. This is the root container element from [Universal Test Renderer](https://github.com/mdjastrzebski/test-renderer).
+Returns a pseudo-element container whose children are the elements you asked to render. This is the root container element from [Test Renderer](https://github.com/mdjastrzebski/test-renderer).
 
 The `container` is safe to use and provides access to the entire rendered tree. It's useful when you need to query or manipulate the entire rendered output, similar to how `container` works in [React Testing Library](https://testing-library.com/docs/react-testing-library/other#container-1).
 

website/docs/14.x/docs/guides/faq.mdx

@@ -8,7 +8,7 @@ React Native Testing Library does not provide an entire React Native runtime sin
 or iOS simulator/Android emulator to provision the underlying OS and platform APIs.
 
 Instead of using React Native renderer, it simulates only the JavaScript part of its runtime
-using [Universal Test Renderer](https://github.com/mdjastrzebski/test-renderer) while providing queries
+using [Test Renderer](https://github.com/mdjastrzebski/test-renderer) while providing queries
 and event APIs ([User Event](docs/api/events/user-event), [Fire Event](docs/api/events/fire-event)) that mimicking certain behaviors from the actual runtime.
 
 You can learn more about our testing environment [here](docs/advanced/testing-env).

website/docs/14.x/docs/guides/troubleshooting.mdx

@@ -2,17 +2,17 @@
 
 This guide describes common issues found by users when integrating React Native Test Library to their projects:
 
-## Matching React Native, React & Universal Test Renderer versions
+## Matching React Native, React & Test Renderer versions
 
 Check that you have matching versions of core dependencies:
 
 - React Native
 - React
-- Universal Test Renderer (automatically installed with RNTL)
+- Test Renderer (automatically installed with RNTL)
 
 React Native uses different versioning scheme from React, you can use [React Native Upgrade Helper](https://react-native-community.github.io/upgrade-helper/) to find the correct matching between React Native & React versions. In case you use Expo, run `npx expo install --fix` in your project to validate and install compatible versions of these dependencies.
 
-Universal Test Renderer is automatically managed as a dependency of React Native Testing Library and is compatible with React 18 and React 19.
+Test Renderer is automatically managed as a dependency of React Native Testing Library and is compatible with React 18 and React 19.
 
 Related issues: [#1061](https://github.com/callstack/react-native-testing-library/issues/1061), [#938](https://github.com/callstack/react-native-testing-library/issues/938), [#920](https://github.com/callstack/react-native-testing-library/issues/920)
 

website/docs/14.x/docs/migration/v14.mdx

@@ -4,15 +4,15 @@ This guide describes the migration to React Native Testing Library version 14 fr
 
 ## Breaking changes
 
-### Universal Test Renderer replaces React Test Renderer
+### Test Renderer replaces React Test Renderer
 
-In v14, React Native Testing Library now uses [Universal Test Renderer](https://github.com/mdjastrzebski/test-renderer) instead of the deprecated `react-test-renderer` package. Universal Test Renderer is a modern, actively maintained alternative that provides better compatibility with React 19 and improved type safety.
+In v14, React Native Testing Library now uses [Test Renderer](https://github.com/mdjastrzebski/test-renderer) instead of the deprecated `react-test-renderer` package. Test Renderer is a modern, actively maintained alternative that provides better compatibility with React 19 and improved type safety.
 
 **What changed:**
 
 - The underlying rendering engine has been switched from `react-test-renderer` to `test-renderer`
 - This change is mostly internal and should not require code changes in most cases
-- Type definitions have been updated to use `HostElement` from Universal Test Renderer instead of `ReactTestInstance`
+- Type definitions have been updated to use `HostElement` from Test Renderer instead of `ReactTestInstance`
 
 **Migration:**
 
@@ -48,7 +48,7 @@ import type { HostElement } from 'test-renderer';
 
 **Note:** Most users won't need to update type imports, as React Native Testing Library now exports the necessary types directly.
 
-For more details, see the [Universal Test Renderer documentation](https://github.com/mdjastrzebski/test-renderer).
+For more details, see the [Test Renderer documentation](https://github.com/mdjastrzebski/test-renderer).
 
 ### `container` API reintroduced
 
@@ -57,7 +57,7 @@ In v14, the `container` API has been reintroduced and is now safe to use. Previo
 **What changed:**
 
 - `screen.container` is now available and safe to use
-- `container` returns a pseudo-element container from Universal Test Renderer
+- `container` returns a pseudo-element container from Test Renderer
 - The container's children are the elements you rendered
 - `UNSAFE_root` has been removed
 
@@ -499,7 +499,7 @@ it('should press button', () => {
 
 ### Text string validation now enforced by default
 
-In v14, Universal Test Renderer automatically enforces React Native's requirement that text strings must be rendered within a `<Text>` component. This means the `unstable_validateStringsRenderedWithinText` option has been removed from `RenderOptions`, as this validation is now always enabled.
+In v14, Test Renderer automatically enforces React Native's requirement that text strings must be rendered within a `<Text>` component. This means the `unstable_validateStringsRenderedWithinText` option has been removed from `RenderOptions`, as this validation is now always enabled.
 
 **What changed:**
 

website/docs/14.x/docs/start/intro.md

@@ -6,7 +6,7 @@ You want to write maintainable tests for your React Native components. As a part
 
 ## This solution
 
-The React Native Testing Library (RNTL) is a lightweight solution for testing React Native components. It provides light utility functions on top of [Universal Test Renderer](https://github.com/mdjastrzebski/test-renderer), in a way that encourages better testing practices. Its primary guiding principle is:
+The React Native Testing Library (RNTL) is a lightweight solution for testing React Native components. It provides light utility functions on top of [Test Renderer](https://github.com/mdjastrzebski/test-renderer), in a way that encourages better testing practices. Its primary guiding principle is:
 
 > The more your tests resemble how your software is used, the more confidence they can give you.
 

website/docs/14.x/docs/start/quick-start.mdx

@@ -13,7 +13,7 @@ Open a Terminal in your project's folder and run:
   }}
 />
 
-This library uses [Universal Test Renderer](https://github.com/mdjastrzebski/test-renderer) as its underlying rendering engine. Universal Test Renderer is automatically installed as a dependency and provides better compatibility with React 19 and improved type safety compared to the deprecated `react-test-renderer` package.
+This library uses [Test Renderer](https://github.com/mdjastrzebski/test-renderer) as its underlying rendering engine. Test Renderer is automatically installed as a dependency and provides better compatibility with React 19 and improved type safety compared to the deprecated `react-test-renderer` package.
 
 ### Jest matchers