Booru Test List

You won't find this node by searching for a feature, because it isn't one. Booru Test List is the author's own prompt-testing drawer, exposed as a dropdown. And once you get that, it's genuinely useful: if you spend evenings A/B-ing samplers, schedulers, or LoRA strengths, this hands you eight fixed scenes to throw at every experiment - so your results actually compare.

What's in the drawer

Pick test_name and you get eight scenarios - Smith the blacksmith, a corporate shoot, a market, dawn, breakdance, a greenhouse, a scholar, a meal - each a hand-tuned Booru-style tag list (1boy, dwarf, brown hair, braids, beard...). That's Danbooru vocabulary, which means it's built for Illustrious, NoobAI, and Pony-family models, where a correct tag beats a sentence every time. The scenes are clearly chosen to stress composition and lighting, which is exactly what you want from a regression test.

How it works

Mechanically it's dead simple. The node reads a text file from the pack's own tests/booru/ folder - the pack registers that directory as a ComfyUI "booru" folder at load time, so you don't copy anything anywhere and there are no model downloads. Each file is split on the ######## separator line: everything before feeds POSITIVE, everything after feeds NEGATIVE. Two string outputs, wire them straight into a CLIP Text Encode (positive and negative).

The one deliberate quirk: the node returns NaN from IS_CHANGED, which forces ComfyUI to re-run it on every single queue. That's intentional - a test node that cached would be useless - but it also marks everything downstream dirty, so don't leave it in a workflow you care about caching. It's a test rig, not a production component.

Installing it

Install is just the pack. ComfyUI Manager, search "comfyui-fams", or:

cd ComfyUI/custom_nodes
git clone https://github.com/famellad/comfyui-fams

then restart ComfyUI. One gotcha that bites people who install this pack just for this node: comfyui-fams needs ImageMagick plus the Python wand binding installed, or the whole pack fails to register. One of the pack's modules imports wand at the top, and a failed import takes every node down with it - this node included, even though it never touches wand. If your Fams menu is empty after install, that's the first thing to check.

If a file ever reads back as "Error reading file", the separator or filename got mangled - otherwise this thing just works. It won't change your life. But the next time you're convinced sampler X beats sampler Y, it'll stop you from trusting a two-prompt sample size.