# Flow testsuite for testing core node functionality
**URL:** https://discourse.nodered.org/t/flow-testsuite-for-testing-core-node-functionality/97106
**Category:** Share Your Projects
**Created:** [17 May 2025 08:07 UTC](https://discourse.nodered.org/t/flow-testsuite-for-testing-core-node-functionality/97106 "2025-05-17T08:07:18Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@gregorius](https://discourse.nodered.org/u/gregorius)
#### Post date: [17 May 2025 08:07 UTC](https://discourse.nodered.org/t/flow-testsuite-for-testing-core-node-functionality/97106/1 "2025-05-17T08:07:18Z")
Hi There,
As part of my [Erlang-RED](https://github.com/gorenje/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](https://github.com/gorenje/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](https://flows.nodered.org/node/@gregoriusrippenstein/erlang-red-unittest) 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](https://flows.nodered.org/node/@gregoriusrippenstein/node-red-contrib-flowhub), PR @ GitHub or as comment here.
---
### Author:  [@AllanOricil](https://discourse.nodered.org/u/AllanOricil)
#### Post date: [17 May 2025 17:24 UTC](https://discourse.nodered.org/t/flow-testsuite-for-testing-core-node-functionality/97106/2 "2025-05-17T17:24:53Z")
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.
---
### Author:  [@gregorius](https://discourse.nodered.org/u/gregorius)
#### Post date: [18 May 2025 12:01 UTC](https://discourse.nodered.org/t/flow-testsuite-for-testing-core-node-functionality/97106/3 "2025-05-18T12:01:20Z")
This [line](https://github.com/gorenje/erlang-red-unittesting-nodes/blob/3079ed94ccb5fcc1d63f475bf23a65058c03f4bc/plugins/sidebar.html#L513)
That bit of code is from a [discussion](https://discourse.nodered.org/t/tutorial-create-a-sidebar-plugin-and-persist-the-data-in-a-config-node/82020/30) on how best to initialise side bar plugins. It also resulted in this [fix](https://github.com/node-red/node-red/commit/e1f2e0656b15b7d1de564295a5afdf6feeae6d7a) in Node-RED.
Btw that code over at Github isn't the single source of truth, this [flow](https://flowhub.org/f/ef91cb280e1bfd72) is the codebase.