Feature Requests
298 results found
-
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 -
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 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 -
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 -
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 -
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 -
xUnit tests search: take into account attributes derived from [Fact]
xUnit tests search: take into account attributes derived from [Fact]
Details
xUnit allows to extend its functionality by deriving from [Fact] attribute, e.g. is allows to generate test case parameters by using such approach. It even has OOTB [Theory] attribute which is derived from [Fact] (see https://github.com/paulecoyote/xunit/blob/master/Main/xunit.extensions/DataTheories/TheoryAttribute.cs).
The problem is that NCrunch does not "see" tests marked by attributes derived from [Fact] (e.g. [Theory]) unless you explicitly have at least one "Fact" test in your test assembly.
2 votes -
When showing coverage for specific tests show icon against them in 'NCrunch Tests' view
When I show coverage for a specific test I trace through the code paths which are being executed using the per line coverage, however sometimes I then need to debug through that test, it would be nice if I could easily see which test is currently showing coverage so I can debug it
2 votes -
Provide a smoother upgrade path for Grid Node Server - (backwards) compatability or run in parallel.
At the moment, the grid node servers must be updated at the same time as all VS clients.
Either allow mismatched versions of NCrunch in VS and distributed nodes, or allow multiple instances of the grid node server on the same machine.
This is holding back our adoption of v2.8 - whether we install the server first or ask developers to upgrade their client first, we have a period where nobody has distributed processing.
2 votes -
Reorganize settings based on events, not entities
E.g.,
On build Failure:
Outer Circle Colour – Dark Brown
Text Colour – Green
Line Marker Colour – Brown
Background music – Ride of the ValkyriesOn Test Failure
Outer Circle Colour – Red
Text Colour – Black
Line Marker Colour – Red
Background music – God Defend Visual Studio
….The reason is that humans are conditioned to think in terms of events. When “this” happens, I want “That”.
I.e., instead of thinking of
an entity, and all the events that can affect it,
we human like to consider
an event, and all the entities that are affected by…2 votes -
Show risk information in code margin.
Show colour indicator and number indicator. Number will show how many tests cover that method and colour will say if its enough tests to fill safe.
2 votes -
Allow coverage marker colour to be defined for tests in progress
When tests execute the colour of the coverage markers darken. This is very useful for determining when affected tests have completed. However, the contrast is too subtle. It would be good if this could be changed in the 'Coverage Markers' configuration section. Either with an absolute colour or at least to have control over the percentage of darkening.
2 votes -
Remote server: Conditionally run tests depending on which remote server they are running on.
Scenario:
I have http integration tests which will report results in one way locally (due to IIS custom errors) and one way remotely. Thus for tests verifying the corretc "remote" response I would like them to run on a grid node that is not running on my local machine.The current "Capabilities" is not attractive since that is set on grid node server itself and requires project-specific user configurations on each grid node server (which annoys the developers if they are running them on their dev machines if I will need to interrupt to tweak custom project settings).
Possible solutions…
2 votes -
Make NCrunch grid performance measurable
Provide some kind of programmatic access to performance indicators that are able to report the performance of a ncrunch grid, e.g. provide access to the duration of a full-end-to-end test. This would enable things like auto-scaling a grid.
2 votes -
Support Directory.build.props
We use Directory.build.props a lot. For example to define variables (within PropertyGroup) and use these variables as TargetFramework in the project files.
Please support this approach the same way msbuild support it.
1 vote -
Gutter indicator at top to indicate if file has tests that fail
Similar to ReSharper/Rider sidebar functionality of a top marker to quickly show "no issues/warning/error" for current file, it would be nice with similar for NCrunch test state for current file.
Scenario: I am working through a lot of failing tests after refactoring and would like to quickly see in current file (in my case test fixture files) if it has failing tests without having to navigate to it in the NCrunch Tests window.
Similar/same(?) to https://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/5827460-test-pass-fail-in-enhanced-scroll-bar-or-r-scroll
1 vote -
Test attribute to watch a file/folder for changes
Scenario: I have long running test (~30s) that uses EF Migrations to check if there are pending changes in data model (no db interaction). Since this is resource intensive I would like this test only to execute if
it is outdated with respect to a folder/file name match in an attribute for it.Example of usage
[Test]
[FileWatcher("test/contexts/models/*")]
public void MigrationsAreUpToDate() {
//... only treat as impacted if test was last executed before modification date of any files in <slnDir>/test/contexts/models
}(Related to the old no longer working feature of being able to find impacted tests via consumed resource files,…
1 vote -
Add process ID as column in NCrunch Tests Window
Scenario: I am troubleshooting static initialization issues in tests, where some tests are not behaving as expected when executed within same process as other tests.
It would be helpful if I can have a column with the process ID so I easy can group tests together in order to troubleshoot.Workaround: Log Process ID and try to find tests using same Process ID by comparing Trace Output for each test, but this is very tedious.
1 vote
- Don't see your idea?