NCrunch sometimes ends up in a state where it tells me there are more tests to run even though there is no activity in the processing queue. Is there a way for me to diagnose why this might be the case so that I can resolve it?

Here is a screenshot:
* https://drive.google.com...L2PmpzK/view?usp=sharing

Hi Remco

I re-ran all the tests, and a different, larger set is not running. I couldn't see any tests with a value in the "Required Capabilities" column, even when I showed passing tests in the view.

* https://drive.google.com...yGqEwUq/view?usp=sharing

Based on the two screenshots I've posted, it's not the same set of tests each time because the number of tests queued is different.

I had a look at the statuses of the tests when the problem occurs, and there was no obvious link from the status to the number of queued tests. For example, when 151 tests were queued but not running, I looked at the number of tests in each status, and the only possible combination of statuses where the total number of tests in these statuses came to 151 was: Ignored, Passed last run, Pending, Impacted, and Passed last run, Impacted. This doesn't make much sense to me because I wouldn't have expected `Ignored` tests to be marked as queued, so I don't think the status of the test will show me which ones are queued but not yet run.

I'll submit a bug report when I get a chance to reproduce the issue again.

UPDATE: submitted bug report via the Submit Bug Report tool. I also re-analysed the statuses in the NCrunch Tests window, and the total number of queued tests was 151 again. This may have been composed of tests in the following statuses:
Passed last run (30 tests), Pending, Impacted (32 tests), and Passed last run, Impacted (89 tests). Does it make sense that tests with those statuses would get into this state?

I now have 122 tests queued for execution, with none being processed. There are exactly 122 tests with a "Pending" status in the processing queue.

I've run the tests under the new version and submitted a bug report.

Looking at the tests that are queued for execution, it seems that the bulk of them are tests that are excluded by the engine mode that I've configured. Would you expect tests that don't qualify for the current engine mode to be listed as "queued for execution"?

Is there a way to export the contents of the NCrunch Processing Queue window via CSV like we can with the NCrunch Tests window?

Thanks, Remco. That's resolved the problem with not all the tests being run. Interestingly, we've had a similar setting in place for a few years, since NCrunch 2, and haven't noticed the problem until recently.

You're welcome. Happy to help :)