comfyui-testing-and-qa
Skill4 starsChanged 44 days agoMITView on GitHub
Use when adding or repairing tests, CI, workflow tests, custom-node QA, regression checks, compatibility matrices, or when deciding how to prove a ComfyUI change works.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- comfyui-api-and-sdkSkill
- comfyui-core-runtimeSkill
- comfyui-custom-node-backendSkill
- comfyui-developmentSkill
- comfyui-frontend-extensionSkill
- comfyui-packaging-and-registrySkill
- comfyui-performanceSkill
- comfyui-self-maintenanceSkill
- comfyui-subgraphsSkill
- comfyui-upstream-developmentSkill
- comfyui-workflowsSkill
- comfyui-workflow-validationSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Use the cheapest test that can actually catch the regression, then add integration coverage where interface boundaries matter.
- Distinctive: line 31
import/load tests for extension packaging.
- Distinctive: line 47
Do not automatically run large model downloads, long generations, paid Cloud jobs, or broad GPU matrices without the user asking or an …
- Distinctive: line 51
Before calling testing complete:
- Distinctive: line 54
run the focused suite that covers the changed contract.
- Distinctive: line 56
do not silently skip expensive or unavailable tests.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ComfyUI Testing and QA
Sources
Relevant official tools include:
- target project's own test suite;
Comfy-Org/ComfyUI-test-framework;Comfy-Org/comfy-qa-tools;Comfy-Org/custom-node-qa;Comfy-Org/Comfy-PR;Comfy-Org/comfyci-dashboard;- frontend/core repository tests.
Inspect current tool docs before invoking them.
Test pyramid
Use the cheapest test that can actually catch the regression, then add integration coverage where interface boundaries matter.
Typical layers:
- pure unit tests for transformations/helpers;
- schema/registration tests for node interfaces;
- import/load tests for extension packaging;
- frontend unit/type/build tests;
- workflow preflight;
- workflow execution tests;
- multi-version or GPU matrix only when the supported contract requires it.
Regression rule
For a bug fix, add a test that fails for the old behavior and passes for the fix whenever practical.
Environment truth
Record enough environment/version information to interpret failures. A GPU or dependency mismatch can otherwise look like an application regression.
Expensive tests
Do not automatically run large model downloads, long generations, paid Cloud jobs, or broad GPU matrices without the user asking or an established project test command that clearly implies them.
Acceptance gate
Before calling testing complete:
- include a regression test for a bug fix when practical;
- run the focused suite that covers the changed contract;
- record enough environment information to interpret hardware or dependency failures;
- do not silently skip expensive or unavailable tests;
- report skipped test layers and the reason.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

