write-unit-tests

Guide unit and integration tests for the tldraw SDK with Vitest patterns.

Updated Aug 23, 2026

Search Tags:#vitest #unit-testing #integration-testing #testing-patterns #tldraw #test-editor

Ready to run

npx skills add https://github.com/arusinova/annarusinova-platform --skill write-unit-tests-arusinova

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-unit-tests
Source: https://github.com/arusinova/annarusinova-platform/tree/main/.claude/skills/write-unit-tests
Command: npx skills add https://github.com/arusinova/annarusinova-platform --skill write-unit-tests-arusinova

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing reliable tests for the tldraw SDK can be time-consuming without a standardized approach. This Skill provides guidance on where to place unit and integration tests, what patterns to follow, and how to structure test files for maintainability.

Core Features & Use Cases

Establishes test placement conventions for core packages (e.g., packages/editor, packages/tldraw) to ensure consistent coverage.
Covers Vitest patterns, TestEditor usage, and test file organization to speed up onboarding and reduce flaky tests.
Enables teams to quickly bootstrap new tests, extend existing suites, and fix failing tests with a clear workflow.

Quick Start

Run the suggested tests scaffolding workflow to create or update unit/integration tests following the described patterns.

Frequently Asked Questions about write-unit-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write unit tests for the tldraw SDK?▼

Unit tests for the tldraw SDK should be placed in the packages/editor or packages/tldraw directories. Utilize Vitest patterns and the TestEditor utility to structure your test files, ensuring reliable coverage and maintainable test suites across the workspace.

What is the best way to organize integration tests in the tldraw workspace?▼

Organize integration tests by placing them within the core packages, specifically packages/editor and packages/tldraw. Following these test placement conventions and file organization patterns reduces flaky tests and speeds up onboarding for new test suites.

Does the tldraw SDK testing workflow require Vitest?▼

Yes, the tldraw SDK testing workflow relies on Vitest patterns to structure and execute tests. The standardized approach uses Vitest alongside the TestEditor utility to speed up test bootstrapping, extend existing suites, and reduce flaky tests.

When should I use TestEditor in my tldraw test files?▼

Use TestEditor in your tldraw test files when bootstrapping unit and integration tests within the core packages. It provides a reusable pattern for test file organization, enabling you to quickly extend existing suites and fix failing tests with a clear workflow.

Why are my tldraw SDK unit tests failing?▼

Your tldraw SDK unit tests may be failing due to inconsistent test placement or a lack of structured Vitest patterns. Following the established test file organization conventions and utilizing the TestEditor utility can help fix failing tests and reduce flaky test behavior.