remove update alias to rerender

Author: mdjastrzebski

src/matchers/__tests__/to-be-on-the-screen.test.tsx

@@ -13,7 +13,7 @@ test('toBeOnTheScreen() example test', async () => {
   const child = screen.getByTestId('child');
   expect(child).toBeOnTheScreen();
 
-  await screen.update(<View />);
+  await screen.rerender(<View />);
   expect(child).not.toBeOnTheScreen();
 });
 
@@ -47,7 +47,7 @@ test('toBeOnTheScreen() on detached element', async () => {
 
   const element = screen.getByTestId('text');
   // Next line will unmount the element, yet `element` variable will still hold reference to it.
-  await screen.update(<ShowChildren show={false} />);
+  await screen.rerender(<ShowChildren show={false} />);
 
   expect(element).toBeTruthy();
   expect(element).not.toBeOnTheScreen();

src/matchers/__tests__/to-be-visible.test.tsx

@@ -169,7 +169,7 @@ test('toBeVisible() on inaccessible view', async () => {
   const test = screen.getByTestId('test', { includeHiddenElements: true });
   expect(test).not.toBeVisible();
 
-  await screen.update(<View testID="test" />);
+  await screen.rerender(<View testID="test" />);
   expect(test).toBeVisible();
 });
 
@@ -190,7 +190,7 @@ test('toBeVisible() on inaccessible view (iOS)', async () => {
   const test = screen.getByTestId('test', { includeHiddenElements: true });
   expect(test).not.toBeVisible();
 
-  await screen.update(<View testID="test" accessibilityElementsHidden={false} />);
+  await screen.rerender(<View testID="test" accessibilityElementsHidden={false} />);
   expect(test).toBeVisible();
 });
 
@@ -211,7 +211,7 @@ test('toBeVisible() on inaccessible view (Android)', async () => {
   const test = screen.getByTestId('test', { includeHiddenElements: true });
   expect(test).not.toBeVisible();
 
-  await screen.update(<View testID="test" importantForAccessibility="auto" />);
+  await screen.rerender(<View testID="test" importantForAccessibility="auto" />);
   expect(test).toBeVisible();
 });
 

src/render.tsx

@@ -81,7 +81,6 @@ export async function render<T>(element: React.ReactElement<T>, options: RenderO
   const result = {
     ...getQueriesForElement(renderer.container),
     rerender,
-    update: rerender, // alias for `rerender`
     unmount,
     toJSON,
     debug: makeDebug(renderer),

src/screen.ts

@@ -22,7 +22,6 @@ const defaultScreen: Screen = {
   },
   debug: notImplemented,
   rerender: notImplemented,
-  update: notImplemented,
   unmount: notImplemented,
   toJSON: notImplemented,
   getByLabelText: notImplemented,

website/docs/14.x/docs/advanced/understanding-act.mdx

@@ -86,10 +86,10 @@ So far we learned that `act` function allows tests to wait for all pending React
 Therefore, we should use `act` whenever there is some action that causes element tree to render, particularly:
 
 - initial render call - `ReactTestRenderer.create` call
-- re-rendering of component -`renderer.update` call
+- re-rendering of component -`renderer.rerender` call
 - triggering any event handlers that cause component tree render
 
-Thankfully, for these basic cases RNTL has got you covered as our `render`, `update` and `fireEvent` methods already wrap their calls in `act` so that you do not have to do it explicitly.
+Thankfully, for these basic cases RNTL has got you covered as our `render`, `rerender` and `fireEvent` methods already wrap their calls in `act` so that you do not have to do it explicitly.
 
 Note that `act` calls can be safely nested and internally form a stack of calls. However, overlapping `act` calls, which can be achieved using async version of `act`, [are not supported](https://github.com/facebook/react/blob/main/packages/react/src/ReactAct.js#L161).
 

website/docs/14.x/docs/api/misc/other.mdx

@@ -11,7 +11,7 @@ function getQueriesForElement(element: HostElement): Queries {}
 `within` (also available as `getQueriesForElement` alias) performs [queries](docs/api/queries) scoped to given element.
 
 :::note
-Please note that additional `render` specific operations like `update`, `unmount`, `debug`, `toJSON` are _not_ included.
+Please note that additional `render` specific operations like `rerender`, `unmount`, `debug`, `toJSON` are _not_ included.
 :::
 
 ```jsx
@@ -33,7 +33,7 @@ Use cases for scoped queries include:
 function act<T>(callback: () => T | Promise<T>): Promise<T>;
 ```
 
-Useful function to help testing components that use hooks API. By default any `render`, `update`, `fireEvent`, and `waitFor` calls are wrapped by this function, so there is no need to wrap it manually.
+Useful function to help testing components that use hooks API. By default any `render`, `rerender`, `fireEvent`, and `waitFor` calls are wrapped by this function, so there is no need to wrap it manually.
 
 **In v14, `act` is now async by default and always returns a Promise**, making it compatible with React 19, React Suspense, and `React.use()`. This ensures all pending React updates are executed before the Promise resolves.
 

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

@@ -63,6 +63,6 @@ See [this article](https://kentcdodds.com/blog/common-mistakes-with-react-testin
 
 :::warning Async lifecycle methods
 
-When using `render`, the lifecycle methods `rerender`, `update`, and `unmount` are async and must be awaited.
+When using `render`, the lifecycle methods `rerender` and `unmount` are async and must be awaited.
 
 :::

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

@@ -35,8 +35,6 @@ test('example', async () => {
 
 ### `rerender`
 
-_Also available under `update` alias_
-
 ```ts
 function rerender(element: React.Element<unknown>): Promise<void>;
 ```

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

@@ -163,7 +163,25 @@ screen.rerender(<MyComponent />);
 await screen.rerender(<MyComponent />);
 ```
 
-##### 4. Update `unmount` calls to await
+##### 4. Replace `update` alias with `rerender`
+
+The `update` alias for `rerender` has been removed in v14. If you were using `screen.update()` or `renderer.update()`, replace it with `rerender()`:
+
+```ts
+// Before (v13)
+screen.update(<MyComponent />);
+// or
+const { update } = render(<MyComponent />);
+update(<MyComponent />);
+
+// After (v14)
+await screen.rerender(<MyComponent />);
+// or
+const { rerender } = await render(<MyComponent />);
+await rerender(<MyComponent />);
+```
+
+##### 5. Update `unmount` calls to await
 
 ```ts
 // Before
@@ -216,6 +234,36 @@ it('should update component', async () => {
 
 For more details, see the [`render` API documentation](/docs/api/render).
 
+### `update` alias removed
+
+In v14, the `update` alias for `rerender` has been removed. You must use `rerender` instead.
+
+**What changed:**
+
+- `screen.update()` has been removed
+- `renderer.update()` has been removed
+- Only `rerender` is now available
+
+**Migration:**
+
+Replace all `update` calls with `rerender`:
+
+```ts
+// Before (v13)
+screen.update(<MyComponent />);
+// or
+const { update } = render(<MyComponent />);
+update(<MyComponent />);
+
+// After (v14)
+await screen.rerender(<MyComponent />);
+// or
+const { rerender } = await render(<MyComponent />);
+await rerender(<MyComponent />);
+```
+
+**Note:** This change is included in the step-by-step migration guide for async `render` above.
+
 ### `renderHook` is now async by default
 
 In v14, `renderHook` is now async by default and returns a Promise. This change makes it compatible with React 19, React Suspense, and `React.use()`.
@@ -290,7 +338,7 @@ unmount();
 await unmount();
 ```
 
-##### 5. Update `act` calls to use async `act`
+##### 6. Update `act` calls to use async `act`
 
 ```ts
 // Before