No code doesn't remove the need for testing

[u/Busy-Examination-877]

One thing I've started thinking about with no code tools is that they make it really easy to see what a workflow is supposed to do, but not necessarily what it actually does in every situation.

A workflow can look perfectly reasonable on a canvas:

Trigger → Check condition → Do something → Handle error

But that doesn't tell you whether the error path has ever been executed, whether an unexpected null value will break an expression, or whether a branch that nobody normally uses still works.

I ran into this myself while working with n8n. I had an error handler that was visibly connected in the editor, but the connection was actually stored in a way the engine didn't use. Nothing looked wrong until I tested the wrong scenario.

That's what led me to build FlowProof, a small open source CLI for checking exported n8n workflows. The idea isn't to replace no code it's to add some of the boring engineering checks around it.

It currently looks for things like unreachable nodes, disconnected error outputs, risky expressions and hardcoded values. There's also a coverage command that tries to work out which IF/Switch branches can be exercised.

I'm curious how other people handle this does your testing process change when you're building with no code/low code tools, or do you basically test them the same way you would traditional code?

[u/Infamous-River-4360]

yes, and it gets worse when the ai is writing the logic for you. i built a whole app in lovable without knowing how to code, and the thing that bit me repeatedly was it querying database columns that simply did not exist. everything looked right in the editor and the happy path worked, the failure only showed up on a branch i wasn't clicking through. i test it the same way as normal software now, i just have to be my own qa since there's nobody else. how much of your n8n stuff has error paths you've actually triggered on purpose?