Feature Requests
298 results found
-
Support for NSpec
I'd love to run my nspec.org tests via ncrunch.
16 votes -
Allow mouse-click navigation on stack trace even when instrumentation is off
When instrumentation is ON you can navigate from error stack trace to the code with a single mouse-click (very similar to ReSharper stack trace explorer).
When instrumentation is OFF then mouse-click functionality stops working because NCrunch-specific paths are used in this case. ReSharper Stack Trace Explorer still works fine and is able to handle stack traces from NCrunch correctly.
Original issue reports is here: http://forum.ncrunch.net/yaf_postst1513_Error-StackTrace-is-not-navigatable-when-instrumentation-is-off.aspx2 votes -
ncrunch "absorb" solution folder structure to organize the tests
Can we have ncrunch "absorb" solution folder structure to organise the tests in the test overview window? We currently have two folders (slow and fast) and resharper adheres to that struture (very convenient).
I'd like ncrunch to do the same. Could you add that to the Tree structure option in the NCrunch Tests window?
6 votes -
Add progress bar to Metrics tree view
I would find the metrics tree view more useful if the code coverage % column had a progress bar in the background. The numbers are great of course, but a progress bar would be much easier to glance at, especially when looking at a large number of rows.
DotCover has a view that shows what I mean well: https://www.jetbrains.com/dotcover/features/img/dotcover-app.png
3 votes -
Offer a VS toolbar to make switching between engine modes quicker (and visible)
NCrunch should offer a VS toolbar to make switching between engine modes quicker (and visible). It's an often-used function and is tedious to do it through the menu.
3 votes -
Add an attribute like [Isolated] which applies to each member of a fixture rather than the fixture as a whole
The [Isolated] attribute currently only provides isolation for the fixture, not each test within it. Where tests need to be isolated, they need to be individually annotated.
It would be nice to have an attribute like [IsolateEachMember] which could apply to each test in a fixture.
4 votes -
Add filter in "test popup" window
So I navigate code and possible spot an issue, I click on line to bring up the "tests covering this line" and I am interested in a test containing a string e.g. "NoOfQueries" but I am a bit overwelmed with the no of tests for this code so I cannot find it.
Current workaround is to pin all tests covering it, and then add a text filter in the Tests window (and then unpin all tests which kindof ruins my current "pinned tests scope").
1 vote -
Synchronize the "NCrunch Configuration" Window with the selected project in "NCrunch Tests" Window
Or add a Toggle Button to enable this mode
1 vote -
1 vote
-
Implement Ctrl+A shortcut in NCrunch configuration grid
For the moment it's possible to select more than one project but only holding Ctrl key and clicking on each project.
3 votes -
Test result icon next to method name
In the text editor when all the test methods are collapsed, we cannot see which test have failed.
If an icon next to the method declaration was also displayed we could know which one needs to be expanded and work on without the need to look at the overall NCrunch test window.
4 votes -
Separate 'successfully completed' and 'failed tasks' in the Processing Queue window
The NCrunch Processing Queue window currently has 3 toggles:
- Pending tasks
- Tasks being processed
- Completed tasksThe last of these has both the successfully completed and the failed tasks. However, I find that confusing and inconsistent:
- The icon on the toggle button is a checkmark. The icon for successful tasks is a checkmark, while the icon for a failed task is a red "X".
- The NCrunch Tests window also has successful and failed "tasks", in this case the tests. However here there are two toggles, one for successful and one for failed tests.
3 votes -
Install the service as "Automatic (Delayed Start)"
Really small change, but can the Grid Node server install with the service option of Delayed Start rather than Automatic.
The only difference is that there will be roughly a 2 minute delay before NCrunch gets started after a server restart, but it means that the server will have had chance to settle down before NCrunch starts running builds and tests.
2 votes -
cover
When collapsing a method have another icon next to it indicating the coverage.
It can have 5 colors:
Black - no cover
Green - 100% covering tests. All tests pass
Red - 100% covering tests with at least one failing test
Blue - Contains some passing tests but also there are lines of code that are not covered by tests
Orange - Contains some failing tests but also there are lines of code that are not covered by tests2 votes -
Allow a test project to be excluded from creating inline code coverage
Inline code coverage is great for unit tests, but when integration tests are also instrumented we lose the granularity of coverage.
N.B Our integration tests are for testing the interaction of our classes either with each other, or 3rd party libraries. So running them in ncrunch and getting test failure notifications straight away is useful for us.
1 vote -
Support Windows Runtime Components
Support C++ Windows Runtime Components. These are used in Windows Store projects. One of the cool things about WinRT is that you can mix and match languages. I'm not talking about running tests against C++, just allow referencing them. Currently even referencing a component breaks NCrunch compilation for the whole solution.
4 votes -
Support more than one workspace base path
I'm using a RAM-drive as my workspace base path and it often gets full (see complementary feature request here: https://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/6673500-cleanup-of-workspace). It would be nice to have a fallback solution so that when the target drive is full, it doesn't block the whole building process. This fallback solution could be the %temp%. I guess the best would be to try all workspaces in order.
So for example, in my case the workspace base path would be:
d:\;%temp%2 votes -
Support IntelliTrace when debugging tests
At the moment I am unable to make use of IntelliTrace when debugging tests using the NCrunch test runner.
I use IntelliTrace frequently while debugging, and find it especially useful when I want to look into ADO.Net calls from ORMs.
4 votes -
Create a 'Kill Currently Running Tests and Execute Selected Tests Immediately' button
The existing 'Run selected test(s) in new process' button just gives the selected tests high priority. This is very irritating when longer running tests are clogging the queue. I often go to the Processing Queue to kill the tests I don't care about so that my test will start sooner. Worse, sometimes the test I want runs together with long tests I don't want, so I can't kill just the long tests without removing my requested test as well. Just run my test, right now! The others can wait.
7 votes -
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…
3 votes
- Don't see your idea?