I believe this is normal PHP behaviour. The parameters within the function call are not executed, only the commas, as they are doing some "work" by separating the parameters. Try placing each comma on a line by itself and testing it again.

In fact, it's interesting to place every token on a line of its own and see what PHP considers executed. All the open parentheses are executed, all the commas, some of the closing parentheses, some of the semicolons, the second plus and the closing brace of the method.

@CJ Dennis , sorry, but we have internal code formatting standards.

The problem is not in php, but in coverage calculation.
It doesn't matter whether php executes a line or not, the algorithm should consider such issues. IMHO

I can't attach a file due to an error in DB collation, this is a screenshot of the example code https://drive.google.com/file/d/0Byxfc0fklW5NbEpKTjFhbVlqcHc/view?usp=sharing

If you use Codeception, which is powered by PHPUnit, which is powered by Xdebug, you'll see that there are four possible statuses for each line:

green - executed during the last run
yellow - dead code. This code is executable, but unreachable. e.g. all the code up to and including the } after a unconditional return;
white - not executable (not 100% accurate, but close enough)
red - not executed during the last run

The results you are getting are already correct. The red lines you want green are actually white in Codeception's HTML coverage report (i.e. Codeception reports 100% coverage of your test file). You need to educate whoever is responsible for your code standards. I would suggest using Codeception to see the issue more clearly. http://codeception.com/docs/11-Codecoverage

They are not covered, but they're also not considered as executable code. What CJ wrote is correct. PHP simply does not see code on these lines:

https://3v4l.org/8YFSF/vld#output

If you start code coverage as follows, you will see the four different states:

xdebug_start_code_coverage( XDEBUG_CC_UNUSED | XDEBUG_CC_DEAD_CODE );