# Node Red Testing Environment

**URL:** <https://discourse.nodered.org/t/node-red-testing-environment/101975>\
**Category:** Feature Requests\
**Created:** [22 October 2026 07:25 UTC](https://discourse.nodered.org/t/node-red-testing-environment/101975 "2026-10-22T07:25:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dimza300](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dimza300/32/108690_2.png) [@dimza300](https://discourse.nodered.org/u/dimza300)\
**Post date:** [22 October 2026 07:25 UTC](https://discourse.nodered.org/t/node-red-testing-environment/101975/1 "2026-10-22T07:25:24Z")

</div>

Hey team! Could we implement a pre-commit or dry-run testing feature before deploying in Node-RED (similar to n8n's test workflow execution)? This would allow us to test our changes safely without disturbing other active users working on different flows or risking overwrite conflicts in a shared environment.
