Feature Requests
290 results found
-
Support NSubstitute
...my favorite, fluent syntax mocking tool.
1 vote -
License server - Show client version
On the license management page, show the client version for each line. This way I know who should update their clients.
2 votes -
Make the test timeout depends on RepeatAttribute (NUnit)
The default timeout is 60 sec. One can change that value but it would be nice if NCrunch could adapt timeout based on the number of repetitions of the same test (in respect of RepeatAttribute of NUnit).
Today, if I specify a timeout of 120 sec, that timeout is applied no matter how much times the test is repeated in the same tests session.1 vote -
User custom performance metrics (displayed with performance metrics)
My prime use case would be counting and measuring SQL queries (would make easier to monitor impact of changes by other developpers).
Hovering the green/red marker next to a line would display the count and total time for each custom metric.
This could be implemented with a simple attribute like NCrunch.MetricAttribute("SQL") that would be added on functions and/or with a IDisposable scope (using(NCrunch.Metric("SQL")).
They would be noop when not compiled by NCrunch.
1 vote -
enable debug on ignored tests
Often I get to the end of a TDD run and create a total integration test. This test necessarily hits dev database and http endpoints. I want to carefully control the execution of this test, not have it run continually. Ergo, I ignore it. Right clicking on the now "ignored" tests, I see the options to debug, but they don't do anything.
It would be perfect if I could step into and debug ignored tests.
1 vote -
Show coverage on LOC even when tests are excluded
We have a lot of integration tests that interact with the database, and as such, we flag these to be excluded from NCrunch using an attribute/customized engine mode.
While that is great, I would still like to be notified that the actual LOC are covered by something. Right now, I get the white dot/"no coverage"
It would be nice to still mark these lines as covered by a test - even if its excluded. Mark it with some other color, and let me drill into the tests in the test suite.
2 votes -
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 -
Allow projects to marked as no parallel execution
We have an integration test that has a setup task that get runs once before the tests execute to create and teardown the integration test database.
The problem with the way NCrunch executes is we get multiple instances of the database continually created (they have GUIDs in the name so they don't clash) but ideally I'd just like to be able to mark the integration test project to run all the tests in a single thread so the NUnit SetupFixture doesn't get run multiple times ... or if the are going to run in multiple threads to stop the reentrance…
2 votes -
Native support for xUnit Collection attributes
Currently xUnit Collection attributes are not prohibiting nCrunch from running tests inside one collection in parallel. So developers require to decorate old tests with nCrunch-related attributes for those test not to be executed in parallel.
7 votes -
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 -
Assign license key to developer name in mylicenses page
I'd like to be able to assign a company seat license to a developer's name. Currently under the https://www.ncrunch.net/User/MyLicenses page I can't figure out which key is being used by which developer.
As my team grows and as developers come and go this becomes a more time consuming process to manage. I'd rather not do this via another spreasheet.
2 votes -
inherit colors from environment
I don't use Windows default colour scheme. Instead, I reduce the amount of light hitting my eyes by using a black background and green text (very retro, ha ha). Some NCrunch windows / dialogs set their background color to grey, which makes green text difficult to read.
So, please, don't override my local settings, just allow your windows / dialogs to use whatever colours I have already set up for myself.
Thanks!
2 votes -
Be able to Bind a key (F5) to run debugger in the current test cursor located in
It would great to use the muscle memory of pressing F5 to debug code, by allowing the functionality of "Right click on a unit test and select Debug starting test in new task runner process" to happen based on where the cursor is currently located.
2 votes -
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 -
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 -
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 -
Add 'Clear search' button next to "Text to search on" in "NCrunch Tests" window
It'd be useful to clean the search text in one click, similar to OOTB VS and other software experience.
Right now we have to focus on the text within the search box, then double click and delete, or backspace a lot.
Out of the box VS test window has that little button to clear the search, as well as other systems do.
Matter of habit and efficiency while working with UI across various apps.
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
- Don't see your idea?