NCrunch and Rider have different Key Bindings for Running Tests.
Like on my machine, I have Ctrl+D on the Rider Test Session Windows to run the Test in Debug Mode.
In NCrunch it is different (I do not even know), so I use the mouse.
Please add an option (Opt In? on demand? But on default is also fine) that NCrunch will look up the existing KeyBinding to the Rider Test Session Tool Window
Actions and set the matching NCrunch Actions to the same KeyBinding in the NCrunch Test Session Windows.
This will remove friction in the daily usage. And will be more friendly to new NCrunch Users.
Keymaps are somewhat of a nightmare for a tool like NCrunch. It's possible to spend months on tooling and specialised integration to try and find a clean way to implement them, and even then they are still not likely to be right.
The approach I've taken is to simply have a set of defaults that are as close to the NCrunch experience in VS as possible (since this is where most NCrunch users have come from), with the intention that people can just change it from there. You'll find all NCrunch shortcuts listed under the keymap options in your Rider configuration. I recommend just setting them to whatever works best for you.
Yeah, most NCrunch have use Visual Studio with NCrunch in VS before... but years ago, so that binding is gone from my memory (opted for JetBrains Binding in 2019 when i left VS and NCrunch, because use also other IDE from them).
New User would also like that.
Yes, I heard from Horror Stories on KeyBinding for Extensions in Visual Studio from an extensions author. I hoped that Rider would be better ;)