Feature Requests
299 results found
-
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 -
ARM support
Please compile / release for ARM as well as x86/x64.
I am looking to run the NCrunch Grid on machines which use ARM chips and noticed there are only x86/x64 builds.5 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 -
Coverage on If statements
Ncrunch does not appear to check all conditions in an if statement for 100% coverage.
i.e. if (x || y) only requires that x is tested, not y.29 votes -
Support Gauge
Please consider adding support for Gauge (http://getgauge.io). Gauge is an open source test platform, started by ThoughtWorks, for writing specification by example. It is similar to Gherkin, only it uses Markdown. Steps are bound to code using StepAttribute binding.
26 votes -
Build on line "commit" insead of each character typed
I would like the ability to be able to set NCrunch to only build my solution and run my tests after a new line of code is entered or an existing line of code has been edited.
I find the feedback I get from VS more than enough while writing my line of code and would much rather have NCrunch working on giving me feedback on my solution up to the point where I added/edited the last complete line of code while typing the next.
This would allow me to run many more test (as NCrunch has the time between…5 votes -
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 -
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 -
Pin test class in test runner rather than pin each test separately
Would be nice to have ability to pin test class to test runner, rather than pinning each newly added test separately. When adding a new feature, you tend to spam quite a few tests in new test class, or to some existing class. If solution is big, and you have many tests, the response time from NCrunch becomes poor. Of course you can pin each task separately when you add them, but when you spam many small tests, it becomes annoying. NCrunch could automatically detect newly added or modified tests in pinned class(es) and run them, ignoring the rest.
9 votes -
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 -
Filter to show running tests.
Hi, I'd like to have a new filter option along side the "show passing/failing/unexecuted/ignored tests" buttons which would allow me to "show running tests". My use case would be to have show enabled for failing, unexecuted, and running tests -- so I can more clearly see what NCrunch is up to at any given moment.
4 votes -
Move ">" test marker up to the method name
This would leave the marker visible when the method is collapsed.
4 votes -
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 -
Option to run all test in current .cs file
I would be nice if I could tell NCrunch to run all tests in the current file.
Often related tests are implemented in the same .cs file. Some of the projects I work on are too large to leave ncrunch running all the time, so an option to just run all tests in a certain file would be really helpful.
5 votes -
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.
3 votes -
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 -
Support NSubstitute
...my favorite, fluent syntax mocking tool.
1 vote -
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
- Don't see your idea?