-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected missing catch node #48
Comments
Hi, in the majority of cases, the tests we have just test the Node in isolation and doesn't depend on other nodes, core or otherwise. So this isn't something this module does much to help with currently. That said, I can see are argument to be made to make it easier to include certain core nodes - like Will take a look at what the best way to include them is. |
I've just published |
Hi, I confirm the change works great. Regards. |
Hi,
working on tests for a node of mine, I have discovered that I must explicitly load the catch node, with something like:
This is quite unexpected, since "standard nodes" are supposed to be already available.
But, even worse, we have to manually load a file, which is a node-red internal file.
IMHO users should not even know about its existence: since it is a single internal file,
it could be deleted/moved/renamed/etc., breaking third-party tests.
So this seems to create a serious usability issue for node-red-node-test-helper by third-party tests.
The question:
Is this truly needed or am I missing something? Or maybe there is a better way? And what is your point of view on this usability issue?
Regards.
EDIT/PS
I have not checked other standard nodes, but the same considerations could apply also to them, if the same loading procedure is required
The text was updated successfully, but these errors were encountered: