Feature Requests
290 results found
-
Shortened name should just be the test name when viewing with Tree Structure set to test
Currently, when I want to view tests in flat list, I set the tree structure to "Test" but all the following columns display the same values
Name, Shortened Name and Full Test Name !
It would be helpful if the Shortened Name just displayed the test name rather than the full namespace.
4 votes -
Show/Hide previously passing, but now out of date tests
When using the engine mode of "Run impacted tests only, other tests manually", the Test Window provides a green question mark indicator next to tests that were previously passing, but are now out of date (at least that's what we believe the green question mark indicates).
We would like to request an enhancement to the Test Window to show/hide the green question mark tests; this would be an icon next to the current four indicators that will toggle the visible tests: Passing (green check mark), Failing (red X), UnExecuted (blue question mark with an eyeball), and Ignored (yellowish circle with…
17 votes -
Enhance 'NCrunch Distributed Processin -> Server Tasks' window with additional information
It would be nice to enhance 'NCrunch Distributed Processin -> Server Tasks' window adding more context.
Right now it shows 'Processing Taks: 1 test(s) in XXXXX.Test', so would be nice to expand on that and show what are the tests being run right now with that task.
1 vote -
Enable columns grouping on both "NCrunch Distributed Processing'" and "NCrunch Tests" window
Please enable grouping on "NCrunch Distributed Processing'" and "NCrunch Tests" window grids so that it would be possible to have extra dimension on grouping servers by capabilities, or tests by "Excecution status".
With dozens servers we have to keep up with the name convention, naming the servers in a specific way. Grouping by capabilities would be a better choice.
Same same with tests - grouping by excecution status, 'failed, being run, passed' would be just awesome to have - similar to out of the box Visual Studio tests window.
1 vote -
Optimize test status refresh between VS reloads on large amount of tests
Once VS loads, NCrunch seems to refresh tests status.
We noticed performance degradation on 500-1000+ tests.
It takes about 10 minutes (1 test per second or somehting) to get the whole suit refreshed on the status.Always '500+' tests are queried for execution, 100 failing, no tests ignored. Hope that VS won't go down, as NCrunch will start that refresh process again from the very beginning.
With current config we have ~1000 tests and 8 Azure VMs in the grid, 4CPU + 8G RAM.
1 vote -
Add confirmation on deleting server node
Please add a confirmation dialog "You sure you want to delete a node" while deleting a server node from the server nodes list.
1 vote -
Support for NSpec
I'd love to run my nspec.org tests via ncrunch.
16 votes -
Add host spot detection.
Add the ability to highlight risky code paths to help a developer focus their attention on un-covered code paths.
Hot spots should be defined by areas of high cyclomatic complexity and low test coverage similar to the functionality found in JetBrains dotCover.
3 votes -
output window hyperlink for logging file and line number in standard visual studio format
The output window currently requires the format "path: line number" which is not the format supported by visual studio. Visual studio windows require "path (line): message".
Please add support for the visual studio standard format to allow hyperlinks to work in all windows.
2 votes -
Allow to run the tests on the grid node while the foreground solution is still compiling
When working with large solutions, it would be great if the grid nodes would already compile/execute tests in parallel while the foreground solution is still compiling in Visual Studio.
For the moment it seems that whenever I trigger a re-build, NCrunch is pausing to wait for completion. As the re-build takes several minutes (5-10), that seems to be a quite large delay to wait for the test results.
My usage scenario is that I have several grid nodes with some RAM drives (having 2-4 GB capacity) and a large solution with around 160 projects. Thus, when executing, some of my…
1 vote -
Test Filter Builder: Enable filtering by Project Name via regular expressions
Test Filter Builder already supports filtering by Full Name with Regular Expression, and it supports filtering by Project Name, but it doesn't appear that there's a way to filter by project name using wildcards/regex.
I've got test projects containing pure unit tests, named .UnitTests as a convention, but the test classes' namespaces are the same as their SUT (system under test) class (the namespaces don't have ".UnitTests" in them).
I'd like to trigger my (pure, fast) UnitTests to run when impacted, but not my integration tests (they're in separate projects named *.IntegrationTests).
1 vote -
Allow user to set color of code coverage marks while a test is executing.
Currently it only goes a few shades light and it's difficult to see if this is in progress or if it's already passed/failed. Being able to set this color to something like orange gives a clear indication that the test is in progress.
Changing the graphic would also work, instead of a green circle it could be a green question mark.
2 votes -
Add median, quartil, percentile or truncated mean to "Marker performance aggregation type"
First run takes offen more time as following ones. Because of small count of runs in typical unittest scenario, the first outlier has too much weight. In this Case median, quartil, percentile or truncated mean are robust.
Ps. It should be simple to implement this. )
2 votes -
Deep code coverage tool
I was thinking about a better code coverage tool. A tool that take longer to run, but show the real thing.
This deep code coverage tool, should test each line of code. If a line is commented, at least one test should fail or an error should be outlined. The tool can do the check and report the lines that are not well covered.
The result it's easier to remove the line or improve our tests for a better code coverage.
1 vote -
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 -
Custom Engine Modes - Dynamic project name regex by changed project name
Hello,
we have the following naming conversion:
Company.ComponentA.Foo.dll
Company.ComponentA.Foo_uTest.dllI want the relevant unit test dlls to be selected based on the changed product projects.
As an addition the mapping should be flexible and support:
1. Just the unit test target of the changed product target should be used
2. All unit test targets of a changed component should be used.Idea:
1. Selection Pattern for the changed project
'^(\w+[.]\w+[.]).*$' // Captures "Company.ComponentA."Then a string.Format line to create the regex pattern for the project name selection:
'^{0}._uTest$' which would lead to "Company.ComponentA.._uTest"
=> All unit tests of…
1 vote -
Custom Engine Modes - Project name matches regex
Hello,
I want to use regex to match project names because in our projects there is a naming rule:<Product-Assembly> has a corresponding unit test target with the name:
<Product-Assembly>_uTestTherefore I want to define a rule like:
Project name matches regex '^.*_uTest$'With best regards,
stefan1 vote -
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 -
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 -
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
- Don't see your idea?