I've got solution with many projects, so I pin only those test that I need at this moment. If I want to pin all tests from assembly, i have to expand this assembly, select all test and pin them. I would like to pin assembly - all tests in this assembly should be pinned/unpinned automatically.

And one more: "unpin all tests"

I've started using pinning because of the problem described in: http://forum.ncrunch.net...r-extended-periods.aspx - pinning only interesting tests makes this problem less frequent. But this is using pinning as a workaround, and pinning should be used for something else.
As I understand, ignoring tests should be used to 'switch off' tests that aren't compatible with nCrunch, and this is a global setting (saved in *.ncrunchproject).
Pinning test is used for showing nCrunch, which tests are important now, for a concrete developer, so pinning should be saved locally for user (I didn't found this in *.ncrunchsolution.user, so I don't know exacly how this works). In this scenario, I think that there is some place for improvment:
- another Engine mode: "Run pinned tests at high priority, others in background"
- in "Run pinned tests automatically, others manually" way to run all tests (pinned and not pinned) - tests tree doesn't have common root, so you can't run them in one click. I work with 'NCrunch Test' window showing only failing tests (in this mode it shows pinned passing tests too - very handy), so selecting all tests with Ctrl+A doesn't do the trick, because I don't see unpined tests.

Thanks for reply

"Run all tests" will work :)
Customised engine modes sounds interesting, I will wait for them.

I would still like to see the ability to pin all from the assembly level. As it stands now, when I expand the assembly, each class is expanded with its tests, so I have to roll them all up then select them and scroll. On perhaps a tangential note, I use git for source control so I switch branches frequently. I suspect this causes the NCrunch cache to become invalid and I have to resync it, which loses the pin statuses of my tests. Therefore, it would be a good feature for me to easily restore the pin statuses. Especially if I just want to pick an assembly or two germane to what I'm working on.

Thanks

No problem, I will explain how I use the pinned tests, maybe there is better way to accomplish the same thing that I have not tried yet. Usually I leave my engine mode to "Pinned tests automatically/others manually". So what I will do is manually run all tests (minus ignored of course) when I start and end working on a feature. I will then pin the tests in the namespaces I know will be impacted, so just those will fire off. If I run all my tests all the time it can lag my system, and I when I have used the "Impacted tests automatically" mode, it doesn't always run all the right tests and I end up not trusting the red/green indicators as I'm coding along. So I found the pinning to work well since it gives a focused subset to constantly run rather than all tests. If I used Ignore/Unignore to achieve the same thing then it is then harder to manually run everything without having to go unignore. I tend to use Ignore for my integration tests which I only have run on my CI server.

I hope that is clear. If you have suggestions I'm definitely open to them. I really like NCrunch and this pinning/unpinning from the namespace is just a very minor annoyance which I thought would be a fairly simple feature to implement (resurrecting year old post I know, but when I google searched it that is what I found).

Thanks!

I guess I don't care so much about the namespace groupings, the test fixtures within each project/namespace is fine. I definitely like how it works now with having the fixture pinned it automatically pins and runs new tests as they are added. I would probably not care whether it auto-added new testfixtures under the parent project if the project was able to have a pin status attached to it.

I'm curious to know what you mean by changing the grouping mode in the UI? Or does that just mean the menu items are different depending on which level is selected?

I would be interested to know if there was a way to turn off the namespace groupings.

Actually for me, the most annoying thing is that the tree is auto-expanded out to the individual test level by default when it loads tests initially (assuming NCrunch not using cache due to switching branches in version control or something, so it loses prior pin statuses). Thus I open the tests window, navigate to the project, and have to click the roll-up button of every test fixture to fit them on my screen. From that point, I can just highlight the whole lot of testfixtures under a single project, right click, and pin them. Maybe a solution would be just to implement some "Collapse children" function to the context menu, and even a "Select All / Deselect All" functionality then not having to mess with namespace groupings issues.

Maybe this is very specific to my situation. I can provide screenshots or a more detailed description of my projects layout if needed.

Thanks for your responses,
Jon