Hi, thanks for sharing this issue.

Although I realise this is far from ideal, the problem you've described is by design.

When NCrunch is offline, it isn't able to track changes that are made to your solution. To be safe, it assumes that all tests are impacted as soon as it initialises as it cannot be certain if they are still in a 'current' state.

It's recognised that the existing impact detection system used by NCrunch is inadequate and is due for improvement. V3 of NCrunch (expected within the next 2 months or so) will introduce major improvements to the impact detection system, allowing NCrunch to compare assemblies to perform proper IL-level detection of changes. The new detection system will also be working across sessions and will resolve the problem you're experiencing.