I suggest you ...

Provide an engine mode to run only a specific project.

I have a solution that has many projects and each project has an associated test project. When I am working on project A, I only want NCrunch to run ATests, rather than ATests, BTests, CTests, etc. Currently, I can set the engine mode to pinned and pin my tests, but I have to manually pin all of the tests (I can only pin by class at most).

Also, I can setup a custom engine mode, but I would rather not have to have an engine mode per project.

Ideally, I would like a right-click option on a project in the Tests window that would let me tell NCrunch to switch to an engine mode where only tests in that project are run.

Alternatively, the ability to pin all tests (current and ones I may write in the future) in a specific project. Then I could run in pinned-only engine mode without having to navigate through all of the classes in the project and pin them manually.

Note: The reason I want this is because currently my solution is so big that build-all and test-all take a significant amount of time. However, build/test on an individual project is very fast.

3 votes
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)

We’ll send you updates on this idea

Micah Zoltu shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...
  • GreenMoose commented  ·   ·  Flag as inappropriate

    An alternative to the "full blown specific project" thing might be If engine mode supported expanding of environment variables so one can set up 1 engine mode and then modify variable accordingly to get different engine behavior? (Given that it could be taken care of without restarting the NCrunch process, e.g. via WM_SETTINGCHANGE or similar).

    Not as user friendly as original feature request but I guess effort to implement it might decrease significantly.

Feedback and Knowledge Base