Files
ComfyUI_frontend/tests-ui
Jin Yi 515240016c [feat] Add dual mode support to NodeConflictDialogContent and fix TypeScript errors
- Add dual mode support to NodeConflictDialogContent:
  - Support props (conflictedPackages/conflicts) for specific conflicts
  - Fallback to global composable data for SidebarHelpCenterIcon usage
  - Import failed extensions section shows at top with package names
  - Conditional description display for post-What's-New scenarios

- Fix TypeScript errors:
  - PackEnableToggle: Add missing parameter to showConflictModal call
  - InfoTabs: Update conflictResult prop to allow undefined
  - WarningTabPanel: Update conflictResult prop to accept undefined

- Update tests for comprehensive dual mode functionality coverage
2025-07-31 13:58:20 +09: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.