Hi Martin,

NCrunch itself doesn't have direct support for inconclusive tests, even though many of the frameworks it integrates with do have this feature.

This is done for purposes of simplicity. Inconclusive tests would require the engine to have a whole new state representing them including different coloured coverage markers, adjusted aggregation, etc. The existence of this third state would cast doubt around the behaviour of many areas of the engine and make the behaviour of the tool much harder to understand.

NCrunch has a configuration option where you can choose its behaviour when working with inconclusive tests - http://www.ncrunch.net/documentation/reference_project-configuration_consider-inconclusive-tests-as-passing. This allows you to describe to the engine whether you wish to consider these tests as something that requires action on the part of the developer (i.e. failing, the default), or something that is benign and doesn't require attention (passing).