Widget Test 🧪

Widget Test is a development artifact that shipped with the pack. Its docstring says it plainly: it exists for experimenting with widget display modes, specifically testing markdown widgets as spacers between input groups. It takes three text inputs and passes them straight through to three outputs. That's it. There is no randomness, no freezing, no combining - nothing that the rest of comfyui-easy-randomize cares about.

How it works

If you're curious about the mechanism: the node's Python side just echoes text_1, text_2, and text_3 to outputs out_1, out_2, out_3, and also pushes them into a ui payload for spacer widgets. The interesting part lives in the pack's JS extension, which dynamically rebuilds the node's widget list on creation and inserts DOM spacer divs between the text fields - a layout experiment for keeping the Freezable String Combiner's ten slots visually separated. The same extension is what adds those spacer rows to the combiner, which is the actual user-facing result of this experiment.

So when someone shows you a graph with Widget Test in it, it's almost certainly a leftover from the author's own development graph, not a deliberate workflow choice. It's the pack's workshop sawdust, swept into the crate by accident.

The inputs and outputs

• text_1, text_2, text_3 - plain multiline strings in, identical strings out.
• Outputs out_1, out_2, out_3 - pass-throughs, one per input.

If you need to pass several strings through a node for structural reasons, this technically works - but so does a Reroute, and the pack's own String Joiner or Freezable String Combiner gives you actual value for the same effort. Nothing here beats the built-ins.

How to install

It comes bundled with the pack, which installs with no dependencies:

cd ComfyUI/custom_nodes
git clone https://github.com/Ckrest/comfyui-easy-randomize.git

Restart ComfyUI, or install "comfyui-easy-randomize" via ComfyUI Manager. It registers under Local Custom/Test, tucked away from the real nodes.

The verdict

Leave it alone. It's not broken - it just has no reason to be in a production workflow, and its near-zero traffic (it's one of the pack's least-viewed pages) suggests the internet agrees. Knowing what it is saves you the five minutes of confusion I'd otherwise have caused you: you didn't miss a feature, you found the author's scratchpad. The spacer layout it spawned is the real takeaway, and that's already baked into the combiner where it belongs.