Files
ComfyUI_frontend/tests-ui
Christian Byrne 9e78558849 [fix] Update title button tests after onMouseDown method refactor (#5082)
Fixes unit tests that failed after PR #5079 which moved title button
handling logic from LGraphNode.onMouseDown to LGraphCanvas level.

- Updated LGraphNode.titleButtons.test.ts to test canvas-level logic instead of calling node.onMouseDown() directly
- Updated LGraph.test.ts snapshot to reflect removal of onMouseDown function from node serialization
- Tests now mock button.isPointInside() and verify onTitleButtonClick() calls
- Removed unused variables to fix TypeScript compilation

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-authored-by: Claude <noreply@anthropic.com>
2025-08-18 13:33:34 -07:00
..

ComfyUI Frontend Testing Guide

This guide provides an overview of testing approaches used in the ComfyUI Frontend codebase. These guides are meant to document any particularities or nuances of writing tests in this codebase, rather than being a comprehensive guide to testing in general. By reading these guides first, you may save yourself some time when encountering issues.

Testing Documentation

Documentation for unit tests is organized into three guides:

Testing Structure

The ComfyUI Frontend project uses a mixed approach to unit test organization:

  • Component Tests: Located directly alongside their components with a .spec.ts extension
  • Unit Tests: Located in the tests-ui/tests/ directory
  • Store Tests: Located in the tests-ui/tests/store/ directory
  • Browser Tests: These are located in the browser_tests/ directory. There is a dedicated README in the browser_tests/ directory, so it will not be covered here.

Test Frameworks and Libraries

Our tests use the following frameworks and libraries:

Getting Started

To run the tests locally:

# Run unit tests
npm run test:unit

# Run unit tests in watch mode
npm run test:unit:dev

# Run component tests with browser-native environment
npm run test:component

Refer to the specific guides for more detailed information on each testing type.