Feature Requests
298 results found
-
Provide parallelized execution time on Performance markers
Today, NCrunch shows the execution time across all threads on its performance markers.
If code is run in parallel, e.g.
Parallel.For(0, 100000, DoSomething);
the execution time is somehow misleading as it is not the real execution time (eg. 5 seconds) but instead the overall time (eg. 1 minute).
It would be nice if NCrunch would show both times, the actual time needed for the loop as well as the overall time accross all threads.
2 votes -
Fix up layout of custom engine modes test filter builder screen
Currently the "Test Filter Builder" screen in custom engine modes renders very badly. (This is on my 4K laptop screen). See http://imgur.com/Vw5Q1qZ.
This makes the feature barely usable - would be great (and hopefully simple) to fix it.
1 vote -
Hits count on coverage marker circle
When I click on a coverage marker circle, a windows pops up with Test name and execution time information.
It would be nice to have also a third column indicating how much times the test hit the current line3 votes -
Be able to specify which class(es) a test is covering
I've noticed that in our test suite, various classes are showing as having code coverage through implict usage i.e. I'm testing class A, which is using class B within a tested method, and so lines of class B show as covered, when there's no dedicated tests for class B.
Technically class B is getting tested there, but it would be nice if we had an attribute we could optionally use (multiple times per class/method), which specifies which class(es) the class/method is testing.
[Tests<A>]
Then the code analysis will only calculate the LoC coverage for classes specified by the attribute(s) on…
2 votes -
Make the columns resizable without reducing the width of the next colum.
Currently, if you want to make the Name column larger and drag the column separator, it reduces the width of the Status column. I'd rather have the width of the other columns unchanged (with a scrollbar to see the columns that are now outside the window).
In order to reduce the size of the column, simply drag the right column separator to the left.
5 votes -
Show impacted tests filter button
When running only some tests (base on a custom filter) automatically, I would like to see impacted tests that are not in the filter appearing in the Test Window. Adding a filter button "Show impacted tests" will do the trick!
1 vote -
Support for expression body (one line tests)
I would like support for one line tests that use expression body syntax, like the one below. When the test fails I would like to see the red cross with the assert information instead of the red arrow that doesn't give any information of why the test failed
[Test]
public void CanEditIsTrue() => Assert.IsTrue(Result.CanEdit);11 votes -
Build solution for execution
It would be great to take advantage of NCrunch's ability to build a solution in the background with every change; to keep the solution bin's up to date and remove the need to build in visual studio.
1 vote -
Filter tests with build configuration
I would like to add a new condition to the test filter builder, "Build Configuration" that would allow filtering tests based on the currently selected build configuration.
My use case is for integration tests that take a long time to run. I want to run these when the "Release" build configuration is selected. Running all tests in the solution is not suitable as some tests are only for running manually.
1 vote -
Move ">" test marker up to the method name
This would leave the marker visible when the method is collapsed.
4 votes -
Option to select Test Suites dynamically
We run all our tests from CI server (Jenkins).
Currently, we add category to each test case. The NCrunch Engines are predefined (which is a huge number), with "Has category" option. When the runs are triggered, the predefined NCrunch Engine is selected for execution (from Console tool)
This limits our option to trigger different combination of Test Suites from CI server.
Could you please add the option to be able to dynamically create NCrunch Engines or define the Test Suites.
For e.g, all test cases has a unique ID. I would like to pass the test case ID's and NCrunch…
1 vote -
Add short exception message column in Tests window
If there are multiple tests failing, you need to click each one and expand the bottom part of the window to read the text dump. It would save a lot of time if I could see the exception message beside each test. Especially for Asserts where I just want to see the expected value vs the actual value.
Ideally the message is formatted as "{Message} [{ExceptionType}]". AggregateException etc should be unwrapped when creating the short message.
2 votes -
Support NSubstitute
...my favorite, fluent syntax mocking tool.
1 vote -
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
- Don't see your idea?