mirror of
https://github.com/Comfy-Org/ComfyUI_frontend.git
synced 2026-01-26 19:09:52 +00:00
c83f3ff1a7
## Summary Add Jobs API infrastructure in preparation for migrating from legacy `/history`, `/history_v2`, and `/queue` endpoints to the unified `/jobs` API. **This is PR 1 of 3** - Additive changes only, no breaking changes. ## Changes - **What**: - Add Zod schemas for runtime validation of Jobs API responses (`JobListItem`, `JobDetail`) - Add `fetchQueue`, `fetchHistory`, `fetchJobDetail` fetchers for `/jobs` endpoint - Add `extractWorkflow` utility for extracting workflow from nested job detail response - Add synthetic priority assignment for queue ordering (pending > running > history) - Add comprehensive tests for all new fetchers - **Non-breaking**: All changes are additive - existing code continues to work ## Review Focus 1. **Zod schema flexibility**: Using `.passthrough()` to allow extra API fields - ensures forward compatibility but less strict validation 2. **Priority computation**: Synthetic priority ensures display order: pending (queued) → running → completed (history) 3. **Test coverage**: Verify tests adequately cover edge cases ## Files Added - `src/platform/remote/comfyui/jobs/` - New Jobs API module - `types/jobTypes.ts` - Zod schemas and TypeScript types - `fetchers/fetchJobs.ts` - API fetchers with validation - `index.ts` - Barrel exports - `tests-ui/tests/platform/remote/comfyui/jobs/fetchers/fetchJobs.test.ts` - Tests ## Next PRs - **PR 2**: Migrate `getQueue()` and `getHistory()` to use Jobs API - **PR 3**: Remove legacy history code and unused types ┆Issue is synchronized with this [Notion page](https://www.notion.so/PR-7169-feat-Add-Jobs-API-infrastructure-PR-1-of-3-2bf6d73d3650812eae4ac0555a86969c) by [Unito](https://www.unito.io) --------- Co-authored-by: Claude <noreply@anthropic.com>
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 a mixed approach to unit test organization:
- Component Tests: Located directly alongside their components with a
.spec.tsextension - 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 thebrowser_tests/directory, so it will not be covered here.
Test Frameworks and Libraries
Our tests use the following frameworks and libraries:
- Vitest - Test runner and assertion library
- @vue/test-utils - Vue component testing utilities
- Pinia - For store testing
Getting Started
To run the tests locally:
# Run unit tests
pnpm test:unit
# Run unit tests in watch mode
pnpm test:unit:dev
Refer to the specific guides for more detailed information on each testing type.