Testing

Inkfinite keeps correctness checks near the code they protect. Rust tests and Vitest suites cover the document model, interchange boundaries, persistence, and component behavior. Playwright covers editor workflows that require the full web app.

Run the complete unit and integration test suite from the repository root:

pnpm test

Component states

Storybook stories in packages/ui/src/ show shared controls and complete editor states in light and dark themes. Include the states that apply to each component: hover, pressed, selected, disabled, busy, and focus-visible. Menus and popovers should also show dismissal, focus restoration, and placement at viewport edges.

pnpm dev:ui
pnpm --filter @inkfinite/ui storybook:build

Editor end-to-end tests

apps/web/e2e/ contains behavioral and visual Playwright tests. The shared InkfiniteEditor fixture provides canvas operations such as choosing tools, dragging, drawing rectangles, and selecting objects. Use accessible locators for controls and keep coordinate-based input inside these canvas operations.

Behavioral tests assert editor behavior. Visual tests use the @visual tag and Playwright’s toHaveScreenshot() matcher to compare the rendered result with checked-in baselines.

# Run behavioral and visual editor tests
pnpm test:e2e

# Compare visual baselines only
pnpm test:visual

# Review and accept an intentional visual change
pnpm test:visual:update

# Inspect or debug tests interactively from apps/web
pnpm test:e2e:ui

The Playwright setup starts the web app, sets the viewport, waits for fonts, hides screenshot carets, and retains traces on failures. Tests choose the theme through the shared fixture. The suite runs editor tests serially because simultaneous editor startup makes the development server and WebAssembly initialization unreliable.

Review every changed baseline at its captured size before accepting it. Keep the browser channel, fonts, operating system, and headless mode consistent when creating authoritative baselines; these inputs can change rasterization. Playwright writes actual, expected, and diff images under apps/web/test-results/ when a comparison fails.

Use the Playwright suite for UI validation. Use standalone scripts for profiling and publication assets, not a script that starts Vite, launches a browser, and writes screenshots without assertions.

SVG import fixture corpus

fixtures/svg-import/ contains the checked-in inputs used by the Rust SVG import integration tests. Icon and logo inputs are derived from the Catppuccin, Simple Icons, Skill Icons, and Devicon Plain Iconify sets. The corpus also covers nested group transforms, compound even-odd paths, unsupported features and active content, and malformed XML, numbers, paths, and transforms.

The tests check native node counts, source retention, currentColor, path validation, fill rules, warning coverage, and typed failures. Add a minimized fixture when a real SVG exposes an importer regression.

Run the focused suite with:

cargo test -p inkfinite-core --test svg_import_fixtures

The repository lists the sources and licenses for the Iconify-derived inputs in fixtures/svg-import/README.md.