On the other hand, you can "hide" the different code paths in a single algebraic statement, but even if your tests always execute that statement, you've lost in

On the other hand, you can "hide" the different code paths in a single algebraic statement, but even if your tests always execute that statement, you've lost information that you've actually tested the both "paths" of the algebraic statement. I guess it's easier to use a boolean logic example (in JavaScript): return myNormalObject || myDefaultObject(); Your code might always execute the myNormalObject half and return it, and even though your code coverage is 100% of the lines, your tests might miss myDefaultObject() code path. Perhaps some code coverage tools can take this into consideration, though, but then you're back to the original problem..