Hi, thanks for posting.

There are two known ways that this can happen. Both are by design:

1. When using an expected exception attribute (syntax depends on framework), NCrunch can catch the expected exception and report this as an X, but the test is still a pass.

2. When debugging using NCrunch, NCrunch won't update code coverage from the debug session because the debugger can corrupt this data (i.e. caused by pausing over lines when stepping etc). NCrunch will still, however, update the pass/fail result of the test. This means that you can have a test that passed the debug run and has green dots but the coverage data was from a previous run.