Probably splitting hairs here but I’m wondering what peoples preferences are for Tester vs TestFilter
I have a Tester where I’m testing for someAttribute = someValue. this is case one. case two is where is fails the test.
As it is on it’s own it’s not clear at all why or what the point of the test is. Using a TestFilter would let me define the output port names making it much clearer as to the purpose of the test without needing an annotation.
Thoughts? Does anyone do this for the sake of clarity in a workspace?
Tester of TestFilter: Thoughts?
+47- Celebrity
- 2000 replies
+60- 2940 replies
Same for me, not using the Tester as much anymore since the introduction of the TestFilter. I think my main motivation is workspace clarity as well.
+58- Evangelist
- 932 replies
I only use TestFilter.
Being able to name the output ports is my main motivation, it makes the workspace clearer.
+28- Influencer
- 161 replies
Personally, I find TestFilter less readable for simple cases. With a TestFilter you end up drilling into two dialogs to see the condition.
For clarity, I prefer a Tester with a short annotation like “is attr1 in expected range AND attr2 looks like a phone number?” rather than trying to squeeze that intent into port names, which are short and can’t carry much nuance.
That said, TestFilter is great when I need multiple named branches or a bundle of tests in one place. But for a straightforward true/false gate, I stick with a single Tester.
+20- Enthusiast
- 154 replies
I use Tester for simplicity and quick work but then I ended up adding an annotation :) … I shift to TestFilter for more complex stuff.
+27- Enthusiast
- 81 replies
I use TestFilter as it gives me more options to describe output ports.
+43- Influencer
- 279 replies
I use the Tester when I am only wanting to keep the data that is passed and not connect to the fail port. Especially when using simple statements. I like the simplicity of the binary ports, one to connect and keep, the other is left behind/data discarded from process. If I was to use the data from both ports, that is when I use a TestFilter for more clarity on what the difference between the ports is.
+47- Celebrity
- 2000 replies
I've just spent a bunch of time refactoring several of my workspaces to use the test filter in place of testers. For a number of years it's just been me doing the FME stuff, but now im leaving my current job readability had just become way more important.
Thanks all for the input and shame on me for using so many testers all these years
+63- Celebrity
- 1630 replies
I’m forcing myself to use TestFilters more and more simply due to the ability to have multiple output options, and name the ports.
I’ll catch myself adding a testing and often go back and change it to a TestFilter.
Occasionally i do still use a Tester, but only for very simple tests where passed(yes, true)/failed(no, false) are expected outcomes
+20- Contributor
- 24 replies
Agree with others that I like to use TestFilter due to the ability to have multiple ports. However, for binary options true/false, yes/no, I’ll just use a Tester. Of course, always annotating...