Sidebar

Why does the test window not execute my destination and create a file?

0 votes
439 views
asked Jun 20, 2017 by brandon-w-8204 (33,170 points)

2 Answers

+1 vote
The test window by design does not execute destination nodes and send messages to the endpoint(file, socket, ws, ftp etc). The purpose of the test window is to test your mappings and allow you to test without sending data. Once you have completed your testing of your mappings in the test window you can save your channel and send another message from the source or resubmit your message from the messages tab.
answered Jun 20, 2017 by brandon-w-8204 (33,170 points)
0 votes
I added this as feedback to the site as well, but wanted to put it here as well for discussion.

I wanted to test my changes that i made to my final endpoint prior to moving my change to the QA portion where we would test the whole channel to make sure its working properly before moving to production.  Going into F9 test mode and sending a sample message thats already been setup does not hit the final endpoint for execution.  According to this question and answer below thats how its designed.

I would like to request an enhancement that there is a toggle that you can either run the sample message in test mode like it is currently designed, but also when you turn on the toggle it will allow you to test your destination endpoint change that you made without having recreate an end to end test  just so you can see if your change works.  Depending on the source endpoint this could mean a lot of setup to end to end test vs just running through sample message to test a small/large change that you made to your final endpoint
answered Jan 26, 2021 by curt-v-8312 (230 points)
commented Jan 26, 2021 by brandon-w-8204 (33,170 points)
I have added an enhancement request.
...