It's really a pity to see (pun intended), not only here but also in the backup thread, that folks seem to think in scripts and not flows.
To test the functionality of a visual tool, we use textual scripts instead of making the effort of creating a visual solution.
My approach has been to explore visual approaches first and if that fails, to fall (fail?) back to an exec node i.e. script solution or worse case makefile. The advantage is that you learn something about a new paradigm, instead of using the old and trusted textual approach. Plus a visual approach means I don't constantly switch between Node-RED and my Emacs editor - it's all done in NR.
At the end of the day, I don't really care what others do. If the trusted scripting solution plus a bit of AI is your thing, alright sounds lovely. I prefer to find a visual approach and challenge myself to think out-of-the-box, the scripting solution is always available.
Btw I also create my nodes using a node development package. So the obvious interjection: but its a node package with html + js code doesn't really apply since all my code is a flow anyway. I haven't tried adding unit tests to the flows that represent my node packages, but it wouldn't be rocket science.
