agentleFS
TangleMLTangleML/tangle-ui/.claude/skills/vitest-testing/SKILL.md

vitest-testing

Skill104 starsChanged 3 days agoApache-2.0View on GitHub

Vitest unit and component testing patterns. Use when writing unit tests, component tests, or hook tests.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use renderHook with a wrapper for hooks that need providers:

    line 72
  2. Very specific:

    Use act for state updates in hooks:

    line 98
  3. Distinctive:

    Create inline helper functions for test data — don't over-abstract:

    line 160
  4. Very specific:

    Only call queryClient.clear() when the suite uses a QueryClient.

    line 191
  5. Very specific:

    Prefer fireEvent for simple interactions in this project:

    line 221

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Vitest Testing Patterns

Focus tests on the component/hook under test. Assume that dependencies (services, hooks, utilities) are independently tested in their own test files. Only mock what's necessary to isolate the unit under test — don't re-test dependency behavior or create elaborate mock setups for services that aren't the focus of the test.

Setup

  • Framework: Vitest with jsdom environment
  • Globals: describe, it, expect are globally available (no imports needed)
  • DOM matchers: @testing-library/jest-dom is configured in vitest-setup.js
  • Component rendering: @testing-library/react with render, screen, fireEvent, waitFor
  • No MSW: Mock functions directly with vi.mock() and vi.fn(), not HTTP interception

Test File Location

Tests are co-located next to source files:

src/utils/searchUtils.ts
src/utils/searchUtils.test.ts

src/hooks/useIOSelectionPersistence.ts
src/hooks/useIOSelectionPersistence.test.ts

src/components/shared/SuspenseWrapper.tsx
src/components/shared/SuspenseWrapper.test.tsx

Utility / Pure Function Tests

describe("formatDuration", () => {
  it("formats seconds correctly", () => {
    const start = "2024-01-01T10:00:00.000Z";
    const end = "2024-01-01T10:00:30.000Z";
    expect(formatDuration(start, end)).toBe("30s");
  });
});

Component Tests

Render with providers using a wrapper function:

const renderWithProviders = (component: React.ReactElement) => {
  return render(component, {
    wrapper: ({ children }) => (
      <ComponentSpecProvider spec={mockComponentSpec}>
        <QueryClientProvider client={queryClient}>
          {children}
        </QueryClientProvider>
      </ComponentSpecProvider>
    ),
  });
};

it("renders the toolbar", async () => {
  renderWithProviders(<RunToolbar />);
  await waitFor(() => {
    expect(screen.getByTestId("inspect-pipeline-button")).toBeInTheDocument();
  });
});

Hook Tests

Use renderHook with a wrapper for hooks that need providers:

const createWrapper = () => {
  const queryClient = new QueryClient({
    defaultOptions: { queries: { retry: false } },
  });
  return ({ children }: { children: React.ReactNode }) => (
    <QueryClientProvider client={queryClient}>{children}</QueryClientProvider>
  );
};

it("should hydrate component", async () => {
  vi.mocked(hydrateComponentReference).mockResolvedValue(mockHydratedRef);

  const { result } = renderHook(
    () => useHydrateComponentReference(mockComponent),
    { wrapper: createWrapper() },
  );

  await waitFor(() => {
    expect(result.current).toEqual(mockHydratedRef);
  });
});

Use act for state updates in hooks:

act(() => {
  result.current.preserveIOSelectionOnSpecChange(initialSpec);
});
expect(mockSetNodes).toHaveBeenCalledWith(expect.any(Function));

Mocking Patterns

Module mocks with vi.mock()

vi.mock("@/utils/localforage", () => ({
  componentExistsByUrl: vi.fn(),
  getComponentByUrl: vi.fn(),
  saveComponent: vi.fn(),
}));

vi.mock("@monaco-editor/react", () => ({
  default: ({ defaultValue }: { defaultValue: string }) => (
    <pre data-testid="monaco-mock">{defaultValue}</pre>
  ),
}));

vi.mock("@/providers/ComponentSpecProvider", () => ({
  useComponentSpec: () => ({
    componentSpec: mockSpec,
    setComponentSpec: mockSetComponentSpec,
  }),
}));

Function spies

const consoleSpy = vi.spyOn(console, "error").mockImplementation(() => {});
// ...
expect(consoleSpy).toHaveBeenCalledWith("Error:", expect.any(Error));

Global mocks

const mockFetch = vi.fn();
global.fetch = mockFetch;

mockFetch.mockResolvedValue({
  ok: true,
  text: () => Promise.resolve(yamlContent),
} as Response);

Environment variables

vi.stubEnv("VITE_GITHUB_CLIENT_ID", "test-client-id");

Mock Factories

Create inline helper functions for test data — don't over-abstract:

const createMockNode = (
  id: string,
  type: "input" | "output" | "task",
  label: string,
  selected = false,
) => ({
  id,
  type,
  position: { x: 0, y: 0 },
  data: { label },
  selected,
});

Setup / Teardown

beforeEach(() => {
  vi.clearAllMocks();
});

afterEach(() => {
  cleanup();
  queryClient.clear();
  vi.restoreAllMocks();
});

Only call queryClient.clear() when the suite uses a QueryClient.

Assertion Patterns

DOM:

expect(screen.getByTestId("submit")).toBeInTheDocument();
expect(screen.queryByTestId("hidden")).not.toBeInTheDocument();

Mocks:

expect(mockFn).toHaveBeenCalledWith(url);
expect(mockFn).toHaveBeenCalledTimes(1);
expect(mockFn).not.toHaveBeenCalled();

Partial matching:

expect(mockSave).toHaveBeenCalledWith({
  id: expect.stringMatching(/^component-\w+$/),
  createdAt: expect.any(Number),
});

User Interactions

Prefer fireEvent for simple interactions in this project:

const input = screen.getByLabelText("Name") as HTMLInputElement;
fireEvent.change(input, { target: { value: "NewName" } });
fireEvent.blur(input);
expect(mockCallback).toHaveBeenCalled();

Async Testing

await waitFor(() => {
  expect(screen.getByTestId("content")).toBeInTheDocument();
});

await expect(promise).resolves.toBe(expectedValue);

pnpm Scripts

  • pnpm test — Run all unit tests once
  • pnpm run test:coverage — Run with coverage report
  • pnpm run validate:test — Full validate + unit tests

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.