RE

react18-enzyme-to-rtl

Provides migration patterns and philosophy guidance for rewriting Enzyme tests to React Testing Library, supporting React 18 upgrades.

Install

mkdir -p .claude/skills/react18-enzyme-to-rtl && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14888" && unzip -o skill.zip -d .claude/skills/react18-enzyme-to-rtl && rm skill.zip

Installs to .claude/skills/react18-enzyme-to-rtl

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Provides exact Enzyme → React Testing Library migration patterns for React 18 upgrades. Use this skill whenever Enzyme tests need to be rewritten - shallow, mount, wrapper.find(), wrapper.simulate(), wrapper.prop(), wrapper.state(), wrapper.instance(), Enzyme configure/Adapter calls, or any test file that imports from enzyme. This skill covers the full API mapping and the philosophy shift from implementation testing to behavior testing. Always read this skill before rewriting Enzyme tests - do not translate Enzyme APIs 1:1, that produces brittle RTL tests.
562 charsno explicit “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Translate Enzyme shallow/mount to RTL render
  • Convert wrapper.find() to RTL query methods
  • Replace wrapper.simulate() with userEvent interactions
  • Assert visible output instead of internal state
  • Map Enzyme context providers to RTL equivalents
  • Prioritize RTL query methods by accessibility

How it works

The skill provides an API map and a core rewrite template to guide the conversion of Enzyme test patterns to React Testing Library equivalents, focusing on behavioral assertions.

Inputs & outputs

You give it
Enzyme test code for a React component
You get back
React Testing Library test code for the same component

When to use react18-enzyme-to-rtl

  • Refactoring Enzyme unit tests to React Testing Library
  • Updating legacy React test suites for compatibility with React 18
  • Converting wrapper-based implementation tests to user-centric behavior tests
  • Mapping deprecated Enzyme simulate and find methods to RTL query patterns

About this skill

React 18 Enzyme → RTL Migration

Enzyme has no React 18 adapter and no React 18 support path. All Enzyme tests must be rewritten using React Testing Library.

The Philosophy Shift (Read This First)

Enzyme tests implementation. RTL tests behavior.

// Enzyme: tests that the component has the right internal state
expect(wrapper.state("count")).toBe(3);
expect(wrapper.instance().handleClick).toBeDefined();
expect(wrapper.find("Button").prop("disabled")).toBe(true);

// RTL: tests what the user actually sees and can do
expect(screen.getByText("Count: 3")).toBeInTheDocument();
expect(screen.getByRole("button", { name: /submit/i })).toBeDisabled();

This is not a 1:1 translation. Enzyme tests that verify internal state or instance methods don't have RTL equivalents - because RTL intentionally doesn't expose internals. Rewrite the test to assert the visible outcome instead.

API Map

For complete before/after code for each Enzyme API, read:

  • references/enzyme-api-map.md - full mapping: shallow, mount, find, simulate, prop, state, instance, configure
  • references/async-patterns.md - waitFor, findBy, act(), Apollo MockedProvider, loading states, error states

Core Rewrite Template

// Every Enzyme test rewrites to this shape:
import { render, screen, fireEvent, waitFor } from "@testing-library/react";
import userEvent from "@testing-library/user-event";
import MyComponent from "./MyComponent";

describe("MyComponent", () => {
  it("does the thing", async () => {
    // 1. Render (replaces shallow/mount)
    render(<MyComponent prop="value" />);

    // 2. Query (replaces wrapper.find())
    const button = screen.getByRole("button", { name: /submit/i });

    // 3. Interact (replaces simulate())
    await userEvent.setup().click(button);

    // 4. Assert on visible output (replaces wrapper.state() / wrapper.prop())
    expect(screen.getByText("Submitted!")).toBeInTheDocument();
  });
});

RTL Query Priority (use in this order)

  1. getByRole - matches accessible roles (button, textbox, heading, checkbox, etc.)
  2. getByLabelText - form fields linked to labels
  3. getByPlaceholderText - input placeholders
  4. getByText - visible text content
  5. getByDisplayValue - current value of input/select/textarea
  6. getByAltText - image alt text
  7. getByTitle - title attribute
  8. getByTestId - data-testid attribute (last resort)

Prefer getByRole over getByTestId. It tests accessibility too.

Wrapping with Providers

// Enzyme with context:
const wrapper = mount(
  <ApolloProvider client={client}>
    <ThemeProvider theme={theme}>
      <MyComponent />
    </ThemeProvider>
  </ApolloProvider>,
);

// RTL equivalent (use your project's customRender or wrap inline):
import { render } from "@testing-library/react";
render(
  <MockedProvider mocks={mocks} addTypename={false}>
    <ThemeProvider theme={theme}>
      <MyComponent />
    </ThemeProvider>
  </MockedProvider>,
);
// Or use the project's customRender helper if it wraps providers

When not to use it

  • When a 1:1 translation of Enzyme APIs is desired
  • When testing internal component state or instance methods
  • When the project does not use React 18

Limitations

  • Does not provide direct equivalents for Enzyme tests verifying internal state
  • Does not provide direct equivalents for Enzyme tests verifying instance methods
  • Does not support React versions prior to 18

How it compares

This approach shifts from testing internal implementation details to verifying user-visible behavior, which produces more stable and maintainable tests than direct API translation.

Compared to similar skills

react18-enzyme-to-rtl side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
react18-enzyme-to-rtl (this skill)02moNo flagsIntermediate
react-modernization212moNo flagsAdvanced
react-best-practices223moNo flagsIntermediate
frontend-testing113moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry