Here’s my solution(s). Method 1 is my typical brute force approach. Mehtod 2 is largely copied from a post by @alinebessa
I created the workflow while learning Testflows in KNIME Analytics Platform @alinebessa shared with us, which was beneficial for me. Thanks.
Hello everyone,this is my solution.
Hi all, this is my solution.
Hi my Crazy KNIMErs
First of all, I am honoured to have been named COTM this month, and I owe a great deal of gratitude to my colleagues in this weekly challenge, I have learned so much from you, and I hope keep to learning together, Thank you!
As for this week’s challenge, nothing special, my solution is based on the previous solutions of my colleagues.
Here is my solution. As many other participants I also used Integrated deployment, however I tried to make the deployment process automatic: so if the test fails the workflow is never deployed.
Just for the example I created a simple second part of the workflow that follows after the tested part, so if the first part fails, the second part is not even executed. Of course the second part can also be tested, as well as any other part of the workflow.
Eventually if everything is fine all parts are combined together and the final workflow is deployed.
My workflow is very similar to everyone else’s this week. I used used the -Rule Engine- node to change the table to then be able to find the table differences.
Here is the link to my workflow on the hub:
My submission on the challenge 23