Feature Requests
290 results found
-
Make pending test colors configurable
I find finished tests (solid color) difficult to distinguish from pending tests (semi-translucent). I suggest making this configurable, either by allowing the user to specify the alpha for pending tests, or by providing completely separate color choices for pending test states.
1 vote -
Allow the NCrunch Tests window to nest/group by Class
i have my tests setup like this:
public class CalculatorTests{
public class AddMethod{
[Fact]
public void DoesAdd() { /**/ }
}
}I'd like to be able to see the tests grouped by class so I can ignore (for example) all the 'AddMethod' tests. I appreciate I could do this by categories, but it'd be a nice addition.
1 vote -
Hotkey to skip sliding build window
I have a sliding build window turned on as my tests can be fairly intensive to run. Sometimes, however, I'm done making a change and don't want to wait for the sliding window to activate. It'd be nice to have a hotkey to bypass the sliding window on demand.
I take advantage of all the other fantastic hotkeys around running tests immediately, so this isn't a very big deal. But it'd be nice to have. :)
1 vote -
Inline run configuration
I'm a long time NCrunch user but I feel the feedback loop has worsened significantly over time,
An incremental compile on my solution takes ~1s but I often have to wait between 20-40s for ncunch to do the same. (I have no clue if this is because of workspace copying or what).
What I really want from NCrunch is an inline run mode that runs directly on my build output everytime I build (which I do very often)
But currently I can not instruct NCrunch to run directly on my build output or only try to run (build) after a…
1 vote -
Let tests run continuously parallel but randomized - to find concurrency issues
I had the problem that my test setup created some files and sometimes test would interfere because they moved some files. In general i would like to find out if there are concurrency issues in my code or in my tests. I know its not a safe way to find them, but if I could say "these 3 tests should run in parallel for a while" would ease debugging if I already know there is an issue
1 vote -
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 -
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 -
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 -
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 -
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 -
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
-
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 -
Attribute to enable tests with "shared resource" to run on same server within same "session".
Original thread: http://forum.ncrunch.net/yaf_postst1368_Restrict-multiple-tests-to-run-within-same-grid-node-in-console-runner.aspx
This is primarily for the console test runner (or e.g engine mode "run all tests within automatically").
Scenario: I have some integration tests using large test data. This test data is created once and then reused between these tests. When using grid nodes tests using same "test data resource" might end up running in different grid nodes, causing each test creating new test data (which makes the tests slower than if they were run in serial).
It would be nice to have an attribute e.g. [SharedResource("TestBlob")] making all tests with same "shared resource" to be run within…
1 vote
- Don't see your idea?