Flow testsuite for testing core node functionality

Hi There,

As part of my Erlang-RED project, I have now create another repository for collecting together test flows that test the basic functionality of the core nodes (i.e. those that are pre-installed) --> erlang-red-flow-testsuite.

The intention is to have a set of test flows to ensure that the functionality created in Erlang-RED matches the existing functionality in Node-RED.

These flows are created in either Node-RED or Erlang-RED but can easily be interchange between the two.

I also created very simple assert nodes to ensure that what is being tested is correct. These assert nodes work in Erlang-RED (in fact the first nodes that did!) therefore they provide a commonality between the two.

Surprisingly I realised that these tests could also be useful for Node-RED simply to ensure that nothing breaks between releases, so even though the intention was to make sure ErlangRED works, it has become a more generalistic project.

Contribution welcome, can be done either by email to me, via the FlowHub nodes, PR @ GitHub or as comment here.

2 Likes

How is the data-template of your plugin rendered? I could not understand it where you bind the template to the plugin

updated
Never mind, i found it. I though that was something from the editor, but you are querying the html from that script tag and adding it to the sidebar using jquery.

This line

That bit of code is from a discussion on how best to initialise side bar plugins. It also resulted in this fix in Node-RED.

Btw that code over at Github isn't the single source of truth, this flow is the codebase.

1 Like