Hi, thanks for sharing this issue.

Would you be able to submit a bug report after you've had this happen to you? It's possible there's been an internal problem somewhere, and the log in the report may reveal this.

A couple more questions to help narrow this down:

- Does this happen for you on other solutions? For example, if you create a small dummy solution, do you get the same experience?
- Does this happen for the other run test UI options? (Run all tests visible here, Run selected test)
- Which engine mode are you using?

Thanks for sending through the bug report.

It looks like NCrunch's data model for your solution has somehow been corrupted. It isn't clear to me how this has happened, but I'd be very interested in learning more about it if you can find a way to reproduce it. Deleting your NCrunch cache file (stored in the _NCrunch_ folder next to your .sln file) with the engine disabled should resolve the problem.

Ok, it might not seem that way, but this is actually really great news. It means that we have a chance of fixing this!

There is a specific test (or group of tests) that is causing this. We need to know which test it is and why it's special.

It should be possible to find it by running the tests manually. Set your NCrunch to the 'Run all tests manually' engine mode. Try selectively running groups of your tests. If the group contains a corrupt test, the engine will fail to queue everything in the group. The trick is to keep trying until you've narrowed it down to the specific test that is causing the problem.