write-unit-tests

To write Vitest unit tests for tldraw editor behavior, place test files alongside source files and use the Editor class for custom configurations or TestEditor for default shapes and tools. This ensures correct editor automation and reliable state assertions.

Use TestEditor for tldraw integration tests when you need integration-style flows that include default shapes and tools. Use Editor when you require custom configurations, ensuring your Vitest tests target the correct editor automation scope.

The correct file location for tldraw unit tests is alongside the source files, while integration tests belong under the src/test directory. Targeted shape or tool tests should be placed alongside their respective implementations for proper organization.

To mock functions and use fake timers in Vitest for tldraw, apply vi.spyOn for mocking and ensure proper mockRestore cleanup. Use built-in test utilities for fake timers, pointer simulation, and keyboard automation to validate editor behavior safely.

Yes, tldraw testing supports jest-style assertions within Vitest. You can apply practical test utilities for state assertions, shape matching, and undo/redo checks using familiar jest-style assertion patterns alongside Vitest.