Ramonda

Testing

pnpm add -D @ramonda/testing-library @testing-library/dom

import { render, screen, fireEvent } from "@ramonda/testing-library";

test("counts up", () => {
  render(<Counter start={2} />);
  fireEvent.click(screen.getByRole("button"));
  expect(screen.getByText("count is 3")).toBeTruthy();
});

No await, no settle(), no cleanup call. That is the point of the package.

What it adds

The queries you already know — screen, getByText, waitFor, within — are the DOM Testing Library's, re-exported unchanged. Anything you can import from @testing-library/dom, you can import from here.

A few things are Ramonda's, because only Ramonda can know them:

actrenders are batched onto a microtask; only the framework knows when the queue is empty
render / renderHookmounting a Ramonda tree, and diffing a re-render into it
fireEventthe DOM library's, wrapped so the render an event causes is committed before it returns
cleanupruns itself after every test

Config

// vitest.config.ts
export default defineConfig({
  define: { __DEV__: JSON.stringify(process.env.NODE_ENV !== "production") },
  esbuild: { jsx: "automatic", jsxImportSource: "@ramonda/core", target: "es2022" },
  test: { globals: true, environment: "jsdom", setupFiles: ["./test/setup.ts"] },
});

There is no setup file to write for JSX. The compiler imports Ramonda's runtime per file, so nothing has to be put on globalThis and there is no factory name to keep in step with the config.

globals: true is what lets cleanup register its own afterEach.

Cleanup runs after every test

Automatically — and it isn't just tidiness. A leaked container keeps a live tree (its @intervals keep firing, its listeners stay attached) into the next test, and duplicate ids across containers make a scoped query return a node from an earlier test. Both make tests that pass alone fail together, pointing at the wrong file.

Next