I have a lot of test that are semi-autogenerated, fully autogenerated and/or in some way auto-populated. I have often wondered why I have different total test counts locally with NCrunch and remotely on the test server (TeamCity with NUnit 2.6.4 test runner).

For a new project I noticed that when I write something along the following lines (I often use FsUnit, but it is the same idea):



... then I end up with four tests, not eight, in NCrunch. In NUnit test runner (the local windows tool) I see the tests grouped by namespace, classname, methodname and finally testname. In NCrunch I do not have the possibility to select methodname and instead of showing duplicates, it simply throws them away.

How can I get my tests back (if at all, and if not possible, can you consider this a bug report / feature request)? For this new project I can cater for unique names, but with some other projects, they have together close to I think 50k of test cases and it is simply undoable to find and fix all cases of duplicates, if not only because auto-generation makes it non-trivial to fix.

Thanks for pointing me to that link. Is it possible that in the past, where we had discussions that the whole tree only showed green, but the root markers of the tree summarized it as red regardless, that this was caused by tests hidden? And is it likewise possible that when I see long delays, that it may be processing some of those hidden tests?



That is strange, because it is precisely NUnit's own little test runner that gets it "right" and orders them per namespace/method/testname.

This brings me to a request that I think I had quite a while ago: perhaps it wouldn't be too hard, and for me it certainly adds usability, to allow creation of order queries (based on picklists, for instance). Now we are stuck with a sometimes very useful, and sometimes not so useful set of predefined ordering sets. I remember that in the past, esp. for NCrunch, I redesigned the organization of my tests to fit at least one of these particular formats.

Rest assured, apart from the occasional critique, I am still very pleased with the product, it definitely speeds up development (and sometimes totally freezes my pc or visual studio, but that's a price I am willing to pay)!

No, the order of execution is already close to perfect (impacted, fast, failing tests first, etc).

In the top right of the NCrunch Tests view, just to the left of Search, there's a dropdown with a limited, fixed set of ways of ordering the tests in the pane. While this is useful, I would very much like to be able to configure this somehow, create your own order for the tree.



Something that may be relatively painless to do is parameterize what you already have, where a user can reorder these parameters, something like:

{category}/{test}

or:
{fixture}/{category}/{test}

(where the "/" denotes a new tree level, and anything between the slashes are concatenated, then sorted). These examples is one that I miss, for instance, as we have everything in categories, it is useless to have it cluttered with namespace and fixture.

I'm rarely interested in namespaces, they only clutter the view (though on some projects they add value), we usually have fixture, category and testname for our ordering.



The most difficult of sorts is the freeze of Visual Studio (window is still painted, but no response to clicking or settings focus). In some such cases I have found a hidden, modal window using Spy++ (AnkhSvn caused this). More recently, I can't find the cause but it is not yet sure which of the addins, or VS itself, is at the root cause of it.

What happens occasionally, though, is that when VS2015 crashes (or needs to be killed), it doesn't clean up its child processes. In such cases, the NCrunch Host process does not seem to detect that its own host, Visual Studio, is gone. Firing up Visual Studio again then ends up with weird unpredictable behavior (empty screens, no docked windows, or just very slow performance, NCrunch not starting). Killing the NCrunch processes by hands did **not** solve the issue, which is rather weird. A restart of Windows so far seems to be the only remedy.

This last thing is new to VS2015, I did not have that with previous versions.

I will install the latest version of NCrunch soon (I need to update the license), I currently have the latest-but-one version.

Possibly. Since my primary concern is usually productivity, I cannot always try to get to the root of the issue. I do know, for a fact, that both the host process (EngineHost) and at least six or so of the task processes were still running after I killed off devenv.exe.

But let's not bother too much about it now, if it happens again and I can find a way to repro it, I'll let you know ;).

Pity that what looks trivial, isn't (the ordering drop-down). Still, if it cannot easily be made customizable, I'd like to "just" propose a view of category/tests, or category/fixture/tests, as the only current possibility with categories is categories/namespace/fixture/test which is rather cumbersome: the usual purpose of using categories is a different categorization of the tests than already offered by namespaces and fixtures. If you then still have to click through the namespace and fixture, it doesn't add anything to use categories, which is a pity if you have strongly categorized test sets.