# Local testing setup guide for node-red development

**URL:** <https://discourse.nodered.org/t/local-testing-setup-guide-for-node-red-development/31244>\
**Category:** Core Development\
**Created:** [6 August 2020 19:31 UTC](https://discourse.nodered.org/t/local-testing-setup-guide-for-node-red-development/31244 "2020-08-06T19:31:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rorysavage77](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@rorysavage77](https://discourse.nodered.org/u/rorysavage77)\
**Post date:** [6 August 2020 19:31 UTC](https://discourse.nodered.org/t/local-testing-setup-guide-for-node-red-development/31244/1 "2020-08-06T19:31:32Z")

</div>

Greetings-

Is there a guide or set of procedures available for setting your local development environment using the unit test supplied in the node-red core project? I see that the unit tests use grunt, and istanbul, however, upon my first attempt to set them up, they are not working. I have a PR I'd like to push though, but blocked but some of the specific nodejs tests. If I could setup my local development to run these tests, that would be a big help.

Thank you

Rory Savage

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [6 August 2020 22:50 UTC](https://discourse.nodered.org/t/local-testing-setup-guide-for-node-red-development/31244/2 "2020-08-06T22:50:34Z")

</div>

Hi Rory,

it should just be:

1. clone the repository
2. run `npm install` to get the dependencies, including dev dependencies
3. run `grunt` to run the default task which builds the code and runs the unit test suite

When running a travis build through a PR, we also run some automated UI testing on Node 10 - but those tests are not passing reliably yet, so you can generally ignore any failures on Node 10 at the moment. Hoping to get that sorted soon.

---

<div class="post-metadata">

**Author:** ![rorysavage77](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@rorysavage77](https://discourse.nodered.org/u/rorysavage77)\
**Post date:** [7 August 2020 16:50 UTC](https://discourse.nodered.org/t/local-testing-setup-guide-for-node-red-development/31244/3 "2020-08-07T16:50:11Z")

</div>

> [@knolleary](#):
>
> sing reliably yet, so you can generally ignore any failures on Node 10

Thank you! I will try this out right away.

---

<div class="post-metadata">

**Author:** ![rorysavage77](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@rorysavage77](https://discourse.nodered.org/u/rorysavage77)\
**Post date:** [7 August 2020 18:19 UTC](https://discourse.nodered.org/t/local-testing-setup-guide-for-node-red-development/31244/4 "2020-08-07T18:19:23Z")

</div>

My build is now passing with the exception of node 10 (as you mentioned), is there anyway we can get this PR pushed through? Right now I have to manage a local patch and I'd rather have the upstreamed version.

[https://travis-ci.org/github/node-red/node-red/builds/715933399](https://travis-ci.org/github/node-red/node-red/builds/715933399)

Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [6 October 2020 18:19 UTC](https://discourse.nodered.org/t/local-testing-setup-guide-for-node-red-development/31244/5 "2020-10-06T18:19:32Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.