Hi everyone:

I have the following lines of code in a project under test:

if (PropertyTree.Length > 1 && PropertyTree[1] != "P")
{
// Use the P as the start object
o = risk;
CurrentProperty = 1;
}

When I turn on Code Coverage Coloring in the IDE, both lines inside the if-statement are blue, indicating that they were tested.

However, the if statement itself is beige, indicating that only part of that line was tested. Considering that this is an AND operation, I don't see how the if statement could have evaluated to "true" without testing both conditions? (unless the compiler somehow optimized away the second part because it already knew that PropertyTree[1] was not equal to "P", but how then can I turn that behavior off for unit tests?)

Is that a bug in the coloring logic, or am I missing something?

SA.

SA,

We've seen some issues like this before and the end result of our investigations is usually the same. The results is almost always that the compiler is optimizing the IL for statements in ways that the user does not expect. The code coverage tool works exclusivly with code block so it regards that if statement as two totally seperate blocks. And apparently in the generated IL the complier has found some way to short circuit. I don't know any specific way to change compiler behaviour, but what I would recommend taking a quick look at the generated IL for that function. That way you can take a look at the IL to see what part of your execution path is getting skipped and how you can cover it. If you want, you can post that IL back here and I can take a look at it.

Thanks,

Ian