Feature Requests
298 results found
-
Show/Hide previously passing, but now out of date tests
When using the engine mode of "Run impacted tests only, other tests manually", the Test Window provides a green question mark indicator next to tests that were previously passing, but are now out of date (at least that's what we believe the green question mark indicates).
We would like to request an enhancement to the Test Window to show/hide the green question mark tests; this would be an icon next to the current four indicators that will toggle the visible tests: Passing (green check mark), Failing (red X), UnExecuted (blue question mark with an eyeball), and Ignored (yellowish circle with…
17 votes -
Exclude from Metrics Aggregation by wildcard
Allow user to exclude files from Metrics Aggregation by wildcard. As an example, I'd like to exclude all *Designer.cs files from being counted.
17 votes -
Support for NSpec
I'd love to run my nspec.org tests via ncrunch.
16 votes -
Allow the console tool to be run continuously
Im super happy with ncrunch console tool that was just released:
http://www.ncrunch.net/documentation/tools_console-tool
However i would also like it to be able to run as a deamon continuously watching a specified folder/solution using NCrunch excellent incremental build/test features.
Ideally it would output a maximum of N failing tests:
1: *. [NameSpace].Test failed | at line 12 of filename.
2: ....Ideally it would also support verbose output in json/xml so that plugins for other editors can be written.
16 votes -
Option to always start NCrunch disabled
I frequently switch between working copies/branches and since I use an engine mode which is automatically running tests I would to manually enable NCrunch on startup. This since the test suite is very heavy and I might want to open solution without immediately running all tests and/or I need some changes to e.g. "Custom environment variables" so tests are running correctly.
(Now I need to remember to disable NCrunch before closing project, which I most often do not remember. Also the now and then occasional vstudio crashes prevents me from setting this)
15 votes -
Clean up the noise when an AssertFailedException (or similar) is thrown
When an assertion in a test fails, you get the full stack trace of the AssertFailedException, which is noisy. For instance:
Microsoft.VisualStudio.TestTools.UnitTesting.AssertFailedException: Assert.AreEqual failed. Expected:<1200>. Actual:<900>.
at Microsoft.VisualStudio.TestTools.UnitTesting.Assert.HandleFail(String assertionName, String message, Object[] parameters)
at Microsoft.VisualStudio.TestTools.UnitTesting.Assert.AreEqual[T](T expected, T actual, String message, Object[] parameters)
at Microsoft.VisualStudio.TestTools.UnitTesting.Assert.AreEqual[T](T expected, T actual)
at TestInheritance.Tests.RectangleTests.AreaAfterSettingHeightWidth() in d:[some likely really long path]\RectangleTests.cs:line 22Of all the above information, the only pertinent information is the message text of the exception and the bottom of the stack where the assertion failure happened. For instance:
Assert.AreEqual failed. Expected:<1200>. Actual:<900>.
at TestInheritance.Tests.RectangleTests.AreaAfterSettingHeightWidth() in d:\users\floyd.may\documents\visual studio 2012\Projects\TestInheritance\TestInheritance.Tests\RectangleTests.cs:line 22Ideally, for MSTest, NUnit,…
14 votes -
Support for NCrunch on Windows ARM
Windows and VisualStudio is now officially supported by Microsoft https://www.microsoft.com/en-us/d/windows-dev-kit-2023/94k0p67w7581
It would be really useful to test if our code also runs correcly on ARM
12 votes -
Support Expecto
It would be great if NCrunch could integrate with Expecto (https://github.com/haf/expecto).
12 votes -
Mutation Testing
Perform Mutation Testing on the test cases to identify incorrect test cases.
12 votes -
Show code coverage metric in the status bar next to "N"
It would save a few clicks when code coverage would be displayed in the status bar next to "N" or instead of green "N".
Besides, it would be a constant reminder of the current Code Coverage before the commits.12 votes -
Create an option to enable NCrunch only when on A/C power
I almost always develop on a laptop - but sometimes while travelling, and sometimes plugged in. I'd like NCrunch to automatically disable itself when I'm on battery power - it does suck energy like crazy - and then re-enable itself when I'm back on the grid.
12 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 -
Test Window Filter
I would like a filter in the test window that "show only tests that should runs automatically due to configured Engine Mode"
11 votes -
Look at working with Live Share
Visual Studio Live Share is a new collaborative sharing tool that is currently in development for both VS and VS Code.
We are currently evaluating it, and we noticed that annoyingly, there is currently no way to have the nice dots / coverage NCrunch provides to remote guests.
There is a task / issue logged with Live Share https://github.com/MicrosoftDocs/live-share/issues/125 which they seem interested in creating an API eventually.
I think you guys should look at trying to integrate with this... as I believe Live Share looks to be on the right track at the moment... and having NCrunch integrated into…
10 votes -
Using XBox as NCrunch Grid node server
When i'm programming my xbox is idle. it would be awesome if I could run ncrunch builds and test on it.
10 votes -
Option to enter debugger when churn mode makes a test fail
I would like to use churn mode for a single test and make NCrunch enter the debugger as soon as churn mode was able to fail the test.
9 votes -
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 -
Allow specflow scenario outline examples to have their own 'dot marker' in the margin
currently if you have a scenario outline that has several examples there is no way to run a specific example as a test, I can only see the dots in the actual scenario outline and have to then run 'x' number of tests at once (where 'x' is the number of scenario examples)
I'd like a 'dot' by each line in the examples so I could run a specific scenario example on its own or see which example is actually failing
9 votes -
Allow Font Size Control Through Visual Studio's Standard Environment Font Target
Font sizing for the output window is configurable in NCrunch, but font sizing for all other NCrunch windows is not. Please allow users to control NCrunch font sizing through the Visual Studio “Environment” font target. This font target, under "Tools-->Options-->Environment-->Fonts and Colors", is designed specifically for this purpose. See the section “Environment Font” under section “Show settings for” at: https://msdn.microsoft.com/en-us/library/kw7t0545.aspx
Other tools, like JetBrains ReSharper, use this method and it works very well. For those of us who change our font sizes to minimize eye strain (especially when using multiple monitors), this would be a tremendous usability improvement.
8 votes -
to support custom Xunit test cases
As discussed on Twitter (https://twitter.com/remcomulder/status/782892104485703681), I'd like NCrunch to support custom test cases.
xUnit has the support for custom test cases, as the STAExamples of the xUnit Samples demonstrate (https://github.com/xunit/samples.xunit/tree/master/STAExamples). That relies on using your own test discoverer, and specifying a custom test case. When you run that in NCrunch, it fails with a cast exception (https://gist.github.com/tiesmaster/5ecb8bf76aab6ee3cb2bfcc9d4f08e72#file-stacktrace-of-staexamples-on-stable-xunit-packages-downgraded-to-2-1-0).
I think this is a niche feature, since this something that won't be used that often, but still a powerful feature, so it would be really nice to have this.
8 votes
- Don't see your idea?