Feature Requests
297 results found
-
Provide a better filtering on 'Tests being excecuted right now' in 'NCrunch tests' window
With large amount of tests, say 500-1000, it is impossible to see what is going on right now - which tests are being executed.
NCrunch has a specific icon on that, but all such tests are spread across the 'NCrunch tests' window, so we have to scroll here and there to see where NCrunch is up to - which tests are being run right now.
It might not b an issue for unit tests, but integration tests take about 1-2 minutes each to execute, so sometimes it is not clear what's is going on.
Would be nice to have either…
3 votes -
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 'Capabilities' row to 'NCrunch Distributed Processing' window
Please add 'Capabilities' row to 'NCrunch Distributed Processing' window, so that it would be possible to group, sort and identify server at a glance by existing capabilities.
2 votes -
Better exception handing so that VS won't be crushed
Please improve stability/exception handling, provide optional "Submit crash report" window so that we can feedback the exception and other details, and isolate NCrunch from the VS.
We have been seeing unstable behaviour caused by NCrunch while intensively running 1000+ tests across dozens server nodes, all of them cause VS restarted.
That's extremely annoying giving the fact that after the VS crash NCrunch "tries" to pick up tests from the very beginning. We can't complete the whole test suite having crashed somewhere along the way.
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 -
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 -
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 -
Mark tests using TestCaseSource as failed if an error in the method providing the TestCaseData fails
Currently an NUnit test that uses a TestCaseSource attribute to provide the data will not show up at all if the method providing the TestCaseSource data has an exception.
I often end up resorting to Resharper to run the offending test to find out what is going on.
It would be nice if the tests that are failing because their TestCaseSource is not running can show up as failed tests the same way that they do in Resharper.
5 votes -
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 -
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 -
Configurable list of custom ItemGroups to be copied over to workspace
More details - http://forum.ncrunch.net/yaf_postsm7334_Custom-ItemGroups-to-be-copied-over-to-workspace.aspx#post7334
The scenario is coming up with some shared logic to be used by other teams. They have the freedom to add build targets, so list of custom items used isn't fixed.
Currently NCrunch just copies over None or Content or Compile items. Having a configurable list of such items will help avoiding workarounds like adding the item twice.
8 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 -
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 -
Support the new Visual Studio Code IDE
Support the new Visual Studio Code editor.
While it doesn't yet provide extensibility for utils like NCrunch, it is apparently planned for upcoming development, so I wanted to get this on the NCrunch radar.153 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 -
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 -
Support for NSpec
I'd love to run my nspec.org tests via ncrunch.
16 votes
- Don't see your idea?