mirror of https://github.com/Comfy-Org/ComfyUI_frontend.git synced 2026-05-26 16:05:11 +00:00

Files

Alexander Brown 5b48bf67a9 docs: drop misleading pnpm test:unit -- examples (#12460 )

## Summary

- Drop the `--` separator from all in-repo `pnpm test:unit -- <args>`
examples. The separator is unnecessary (pnpm forwards extra args
automatically) and on Windows PowerShell it mangles quoted args like `-t
"restores host values by input name"`, splitting them into multiple
tokens.
- Add a short note in `docs/guidance/vitest.md` explaining the
substring-match semantics of the positional filter and that `-t` matches
`it()`/`test()` names only (not `describe()` blocks).
- Fix `pnpm test:unit -- run <files>` in the backport-management skill:
because `test:unit` is already `vitest run`, the literal `run` token was
a positional path filter that silently narrowed the suite to files whose
paths contain "run".

## Test plan

- [ ] `pnpm test:unit useConflictAcknowledgment` matches
`useConflictAcknowledgment.test.ts`
- [ ] `pnpm test:unit SubgraphWidgetPromotion.test.ts -t "restores host
values"` filters to a single test
- [ ] `git grep "pnpm test:unit -- "` returns no in-repo matches

2026-05-26 03:08:24 +00:00

component-testing.md

refactor: extract composables from VTU holdout components, complete VTL migration (#10966 )

2026-04-10 19:04:16 -07:00

README.md

docs: drop misleading pnpm test:unit -- examples (#12460 )

2026-05-26 03:08:24 +00:00

store-testing.md

chore: remove stale tests-ui config (#10736 )

2026-03-30 11:59:00 -07:00

unit-testing.md

docs: Weekly Documentation Update (#11465 )

2026-05-04 21:37:52 +00:00

vitest-patterns.md

docs: prefer real createI18n over mocking vue-i18n in tests (#11776 )

2026-04-30 14:29:11 -07:00

README.md

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:

Component Testing - How to test Vue components
Unit Testing - How to test utility functions, composables, and other non-component code
Store Testing - How to test Pinia stores specifically

Testing Structure

The ComfyUI Frontend project uses colocated tests - test files are placed alongside their source files:

Component Tests: Located directly alongside their components (e.g., MyComponent.test.ts next to MyComponent.vue)
Unit Tests: Located alongside their source files (e.g., myUtil.test.ts next to myUtil.ts)
Store Tests: Located in src/stores/ alongside their store files
Browser Tests: Located in the browser_tests/ directory (see dedicated README there)

Test File Naming

Use .test.ts extension for test files
Name tests after their source file: sourceFile.test.ts

Test Frameworks and Libraries

Our tests use the following frameworks and libraries:

Vitest - Test runner and assertion library
@testing-library/vue - Preferred for user-centric component testing
@testing-library/user-event - Realistic user interaction simulation
@vue/test-utils - Vue component testing utilities (legacy; new tests must use @testing-library/vue)
Pinia - For store testing

Getting Started

To run the tests locally:

# Run unit tests
pnpm test:unit

# Run a specific test file
pnpm test:unit src/path/to/file.test.ts

# Run unit tests in watch mode
pnpm test:unit --watch

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